Conversation
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233160 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233163 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233165 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233174 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233189 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233191 13f79535-47bb-0310-9956-ffa450edef68
…aven-site-plugin to include the wagon-ssh dependency for scp git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233193 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233200 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233202 13f79535-47bb-0310-9956-ffa450edef68
…pdated maven-site-plugin to include the wagon-ssh dependency for scp git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233205 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233208 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233210 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233212 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233214 13f79535-47bb-0310-9956-ffa450edef68
…w release after voting against the previous release. The support pom.xml has also been changed to remove the incomplete and non-tested 'openid4j' module per thread discussion. git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233524 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233541 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233543 13f79535-47bb-0310-9956-ffa450edef68
…nk, to be worked on for a 1.3 milestone). Reverted pom versions to 1.2.0-SNAPSHOT to re-release. git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233773 13f79535-47bb-0310-9956-ffa450edef68
…nk, to be worked on for a 1.3 milestone). git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233774 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233776 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1233778 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1298909 13f79535-47bb-0310-9956-ffa450edef68
…ScmFailure> to the plugin config git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1331027 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1340194 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1362116 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1363744 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1364194 13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1364198 13f79535-47bb-0310-9956-ffa450edef68
…n the command line now) git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1364199 13f79535-47bb-0310-9956-ffa450edef68
…bject and the session manager is a web-only session manager. git-svn-id: https://svn.apache.org/repos/asf/shiro/branches/1.2.x@1365167 13f79535-47bb-0310-9956-ffa450edef68
…ectj and the maven plugin See also: MASPECTJ-106
The version used previously (1.6.12) doesn't work with Java 7 class files at all. Note that there are still plenty of bugs here: 1. The compiler shouldn't have produced Java 7 files (missing source/target since the use of the toolchain plugin?) 2. The note about having to update some OSGi metadata files seems wrong, there is no such files. And if there where: these files should be managed by the build process!
This requires some changes to the configuration: * <pack200> moved to <pack200><enabled> * the keystore path is (now?) relative to the project directory * the keytool dependencies seem to be missing This looks partially like issues in the webstart plugin, which unfortunately is in the codehaus->github migration bubble. With this change shiro builds with both the toolchain configuration and JAVA_HOME (due to the webstart plugin ignoring toolchains, presumably) pointing to a Java 7 JDK. This makes it possible to compile shiro with Java 8 and up.
If the property is not set, a new cipher will be generated.
This reverts commit 20f2348.
This reverts commit f961b77.
This reverts commit 61aa393.
This reverts commit b70bcef.
Without this the java version is detected as 1.3. Fixes: SHIRO-545
I'm not sure why this was changed, switching back to UTF-8 (from UTF8) Fixes: SHIRO-567
The apache-rat-plugin will cover all files in the project when run from the root. Previously the samples.pom disabled the site plugin execution to work around this issue.
Member
|
Closing this one as 1.2.x is no more maintained. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Well,I'm pretty new to github,and I just want to show you a issue while I'm using 10-minute-tutorial to lean shiro.It uses shiro-root-1.2.0 version to show how to use shiro apis.But when I use
mvn compile exec:javato start the quick start ,I got these errors:$ mvn compile exec:java
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Shiro :: Samples :: Quick Start 1.2.0
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- buildnumber-maven-plugin:1.0-beta-4:create (default) @ samples-quickstart ---
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: cmd.exe /X /C "svn --non-interactive info"
[INFO] Working directory: D:\github\shiro\samples\quickstart
Provider message:
The svn command failed.
Command output:
'svn' ▒▒▒▒▒ڲ▒▒▒▒ⲿ▒▒▒Ҳ▒▒▒ǿ▒▒▒▒еij▒▒▒
▒▒▒▒▒▒▒▒▒ļ▒▒▒
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.301 s
[INFO] Finished at: 2016-04-09T22:24:38+08:00
[INFO] Final Memory: 10M/244M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-4:create (default) on project samples-quickstart: Cannot get the revision information from the scm repository :
[ERROR] Error!
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
After some googling,I work round by adding
<revisionOnScmFailure>unversioned</revisionOnScmFailure>to pom line no. 396
I don't know if you can modify the pom file .Or I think you can give some suggestions to newbies when using the 10-minute-tutorial. Thx