[jira] Updated: (ARCHETYPE-175) archetype returned from local catalog don't have metadata
[
http://jira.codehaus.org/browse/ARCHETYPE-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Kuleshov updated ARCHETYPE-175:
--
Description:
Archetype instance returned from the local catalog don't have metadata, such as
properties. Catalog is obtained like this:
{code}
PlexusContainer container = mavenEmbedder.getPlexusContainer();
org.apache.maven.archetype.Archetype archetype =
(Archetype) container.lookup(org.apache.maven.archetype.Archetype.class);
ArchetypeCatalog catalog = archetype.getLocalCatalog(getId());
Properties properties = ((org.apache.maven.archetype.catalog.Archetype)
catalog.getArchetypes().get(0)).getProperties();
{code}
I expected to see non empty properties for the test project attached at
MNGECLIPSE-612, which I added to the local Archetype catalog like this:
{code}
org.apache.maven.archetypes
maven-archetype-proptest
1.0
Prop test
{code}
was:
Archetype instance returned from the local catalog don't have metadata, such as
properties. Catalog is obtained like this:
{code}
PlexusContainer container = mavenEmbedder.getPlexusContainer();
Archetype archetype = (Archetype) container.lookup(Archetype.class);
ArchetypeCatalog catalog = archetype.getLocalCatalog(getId());
{code}
See test project attached at MNGECLIPSE-612, which I added to the local
Archetype catalog like this:
{code}
org.apache.maven.archetypes
maven-archetype-proptest
1.0
Prop test
{code}
> archetype returned from local catalog don't have metadata
> -
>
> Key: ARCHETYPE-175
> URL: http://jira.codehaus.org/browse/ARCHETYPE-175
> Project: Maven Archetype
> Issue Type: Bug
>Reporter: Eugene Kuleshov
>
> Archetype instance returned from the local catalog don't have metadata, such
> as properties. Catalog is obtained like this:
> {code}
> PlexusContainer container = mavenEmbedder.getPlexusContainer();
> org.apache.maven.archetype.Archetype archetype =
> (Archetype)
> container.lookup(org.apache.maven.archetype.Archetype.class);
> ArchetypeCatalog catalog = archetype.getLocalCatalog(getId());
> Properties properties = ((org.apache.maven.archetype.catalog.Archetype)
> catalog.getArchetypes().get(0)).getProperties();
> {code}
> I expected to see non empty properties for the test project attached at
> MNGECLIPSE-612, which I added to the local Archetype catalog like this:
> {code}
>
>
>
>
> org.apache.maven.archetypes
> maven-archetype-proptest
> 1.0
> Prop test
>
>
>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-175) archetype returned from local catalog don't have metadata
archetype returned from local catalog don't have metadata
-
Key: ARCHETYPE-175
URL: http://jira.codehaus.org/browse/ARCHETYPE-175
Project: Maven Archetype
Issue Type: Bug
Reporter: Eugene Kuleshov
Archetype instance returned from the local catalog don't have metadata, such as
properties. Catalog is obtained like this:
{code}
PlexusContainer container = mavenEmbedder.getPlexusContainer();
Archetype archetype = (Archetype) container.lookup(Archetype.class);
ArchetypeCatalog catalog = archetype.getLocalCatalog(getId());
{code}
See test project attached at MNGECLIPSE-612, which I added to the local
Archetype catalog like this:
{code}
org.apache.maven.archetypes
maven-archetype-proptest
1.0
Prop test
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSTAGE-3) The stage plugin only supports copying from http(s) to scp urls
[ http://jira.codehaus.org/browse/MSTAGE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135824#action_135824 ] azgard commented on MSTAGE-3: - This address also my error i gotwhen i try to move from http-repo to a dav-repo. [INFO] [INFO] org.apache.maven.wagon.providers.webdav.WebDavWagon cannot be cast to org.apache.maven.wagon.providers.ssh.jsch.S cpWagon [INFO] [INFO] Trace java.lang.ClassCastException: org.apache.maven.wagon.providers.webdav.WebDavWagon cannot be cast to org.apache.maven.wag on.providers.ssh.jsch.ScpWagon at org.apache.maven.plugins.stage.DefaultRepositoryCopier.copy(DefaultRepositoryCopier.java:252) at org.apache.maven.plugins.stage.CopyRepositoryMojo.execute(CopyRepositoryMojo.java:93) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > The stage plugin only supports copying from http(s) to scp urls > --- > > Key: MSTAGE-3 > URL: http://jira.codehaus.org/browse/MSTAGE-3 > Project: Maven 2.x Stage Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Maria Odea Ching > Attachments: MSTAGE-3.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-174) The archetype is not configured error does not provide error details
The archetype is not configured error does not provide error details Key: ARCHETYPE-174 URL: http://jira.codehaus.org/browse/ARCHETYPE-174 Project: Maven Archetype Issue Type: Bug Reporter: Eugene Kuleshov When archetype is created (from ide) and does not specify required property, error message does not say what property is not specified. See test project attached at MNGECLIPSE-612 org.apache.maven.archetype.exception.ArchetypeNotConfigured: The archetype is not configured at org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:98) at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:215) at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:130) at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:290) at org.apache.maven.archetype.DefaultArchetype.generateProjectFromArchetype(DefaultArchetype.java:75) at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.createArchetypeProject(ProjectConfigurationManager.java:362) at org.maven.ide.eclipse.wizards.MavenProjectWizard$4.runInWorkspace(MavenProjectWizard.java:227) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-285) Unresolved test-jar dependency during release
[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135812#action_135812 ] Krasimir Chobantonov commented on MRELEASE-285: --- The issue is still present and this only happens when I'm trying to release the project - the building of the project is fine. Maven : version 2.0.8 maven jar plugin : version 2.2 maven release plugin : version 2.0-beta-7 java version "1.5.0_15" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04) Java HotSpot(TM) Client VM (build 1.5.0_15-b04, mixed mode, sharing) The workaround using mvn clean install works but this can't be performed by continuum server automatically. > Unresolved test-jar dependency during release > - > > Key: MRELEASE-285 > URL: http://jira.codehaus.org/browse/MRELEASE-285 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 > Environment: Maven version: 2.0.7 > Java version: 1.5.0_07 > OS name: "mac os x" version: "10.4.10" arch: "i386" >Reporter: Rod Coffin > Fix For: 2.0 > > Attachments: example.jar > > > I have a multi-module project where one project produces a normal jar and a > test-jar > (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). > Another submodule has a test scoped dependency on the test-jar from the first > submodule. For example, this is the structure and produced artifacts for a > small sample (attached) I built to reproduce this behavior: > release-test-jar (parent project) > project-with-test-jar (submodule) > => project-with-test-jar-1.0.jar > => project-with-test-jar-1.0-tests.jar > project-using-test-jar (submodule) > => project-user-test-jar-1.0.jar > When I run a 'clean install' the build succeeds. However, when I run a > 'release:prepare' the build fails with the following error: > 1 required artifact is missing. > for artifact: > com.rfc:project-using-test-jar:jar:1.1 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: > org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: > Missing: > -- > 1) com.rfc:project-with-test-jar:test-jar:tests:1.1 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=com.rfc > -DartifactId=project-with-test-jar \ > -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file there: > mvn deploy:deploy-file -DgroupId=com.rfc > -DartifactId=project-with-test-jar \ > -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar > -Dfile=/path/to/file \ >-Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) com.rfc:project-using-test-jar:jar:1.1 > 2) com.rfc:project-with-test-jar:test-jar:tests:1.1 > -- > 1 required artifact is missing. > for artifact: > com.rfc:project-using-test-jar:jar:1.1 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi
[jira] Commented: (MNG-3580) FATAL ERROR and NPE on start
[ http://jira.codehaus.org/browse/MNG-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135802#action_135802 ] Erik Putrycz commented on MNG-3580: --- According to http://www-128.ibm.com/developerworks/forums/thread.jspa?threadID=206283 this bug is fixed in Harmony Mile Stone 6 and will be fixed in IBM JDK 6.0 SR2. Hard to believe such nasty bugs can be present in JDK code without being caught by a test suite. Erik. > FATAL ERROR and NPE on start > > > Key: MNG-3580 > URL: http://jira.codehaus.org/browse/MNG-3580 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 > Environment: Linux iitm50ws1106 2.6.25.3-2-default #1 SMP 2008-05-10 > 07:46:36 +0200 x86_64 x86_64 x86_64 GNU/Linux > java version "1.6.0" > Java(TM) SE Runtime Environment (build pxa6460sr1-20080416_01(SR1)) > IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64 > jvmxa6460-20080415_18762 (JIT enabled, AOT enabled) > J9VM - 20080415_018762_LHdSMr > JIT - r9_20080415_1520 > GC - 20080415_AA) > JCL - 20080412_01 >Reporter: Erik Putrycz > Attachments: maven.log, MNG-3580.patch > > > Any mvn command does give me the following error message > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] Business Rules Extractor > [INFO] Business Rules Extractor core functions > [INFO] COBOL Parser and ANTLR Tools > [INFO] Business Rules Extractor data model > [INFO] Documentation Extractor module > [INFO] Extractor module > [INFO] Business Rules Navigator > WAGON_VERSION: 1.0-beta-2 > [INFO] > > [INFO] Building Business Rules Extractor > [INFO]task-segment: [install] > [INFO] > > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.project.ModelUtils.mergePluginLists(ModelUtils.java:164) > at > org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleBuildInheritance(DefaultModelInheritanceAssembler.java:366) > at > org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleModelInheritance(DefaultModelInheritanceAssembler.java:168) > at > org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleModelInheritance(DefaultModelInheritanceAssembler.java:61) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:852) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:253) > at > org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:265) > at > org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:197) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1033) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:997) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:59) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:39) > at java.lang.reflect.Method.invoke(Method.java:612) > at org.codehaus.classwor
[jira] Closed: (MRELEASE-267) Whitespaces in artifactId or groupId prevent version update
[ http://jira.codehaus.org/browse/MRELEASE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MRELEASE-267. -- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.0-beta-8 Applied in [r659301|http://svn.apache.org/viewvc?view=rev&revision=659301], thanks René! > Whitespaces in artifactId or groupId prevent version update > --- > > Key: MRELEASE-267 > URL: http://jira.codehaus.org/browse/MRELEASE-267 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: René Link >Assignee: Benjamin Bentmann > Fix For: 2.0-beta-8 > > Attachments: Maven Release Plugin.patch > > > If you have a dependency in your pom that contains whitespaces within the > artifactId or groupId the dependency version will not be updated during a > release:perform. > This circumstance can occur when you are using code formattors on xml files > (pretty print). > > ... > > >de.testpackage > > > someartifactId > > 2.1.4-SNAPSHOT > > ... > > The reason is that the > org.apache.maven.shared.release.phase.AbstractRewritePomsPhase class does not > use the normalize-space xpath function > on the selected tag. > I have attached a patch that is based on revision 556926 (release plugin > version 2.0-beta7) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MJAVADOC-180) aggregation doesn't work for test-javadoc goal
[ http://jira.codehaus.org/browse/MJAVADOC-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-180. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.5 fixed in r659288, snapshot deployed > aggregation doesn't work for test-javadoc goal > -- > > Key: MJAVADOC-180 > URL: http://jira.codehaus.org/browse/MJAVADOC-180 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.4 > Environment: maven-javadoc-plugin 2.3 final > maven-javadoc-plugin 2.4-SNAPSHOT r632385 > Maven version: 2.0.8 > Java version: 1.5.0_13 > OS name: "mac os x" version: "10.5.2" arch: "i386" Family: "unix" >Reporter: Elliot Metsger >Assignee: Vincent Siveton > Fix For: 2.5 > > Attachments: mjavadoc-180.tar > > > When executing 'javadoc:test-javadoc' from a parent project in a multi-module > build, it fails complaining of missing dependencies: > mvn clean -X -e javadoc:test-javadoc > > [DEBUG] embargo-api: using locally installed snapshot > [DEBUG] dspace-api: resolved to version 1.4.2e-20080118.034638-23 from > repository msel.maven.snapshots > [DEBUG] Compiled artifacts for > edu.jhu.library.embargo:embargo-dspace:1.0.0-SNAPSHOT > /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar > /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar > /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar > /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar > /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar > /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar > /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar > /Users/esm/.m2/repository/edu/jhu/library/embargo/embargo-api/1.0.0-SNAPSHOT/embargo-api-1.0.0-SNAPSHOT.jar > /Users/esm/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar > /Users/esm/.m2/repository/org/dspace/dspace-api/1.4.2e-SNAPSHOT/dspace-api-1.4.2e-SNAPSHOT.jar > /Users/esm/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar > > [DEBUG] "cd /Users/esm/idea/workspace/embargo/target/site/testapidocs && > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc" > @options @packages > [search path for source files: > [/Users/esm/idea/workspace/embargo/embargo-api/src/test/java, > /Users/esm/idea/workspace/embargo/embargo-dspace/src/test/java]] > [search path for class files: > [/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/classes.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/ui.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/laf.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jsse.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jce.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/charsets.jar, > /System/Library/Java/Extensions/CoreAudio.jar, > /System/Library/Java/Extensions/dns_sd.jar, > /System/Library/Java/Extensions/j3daudio.jar, > /System/Library/Java/Extensions/j3dcore.jar, > /System/Library/Java/Extensions/j3dutils.jar, > /System/Library/Java/Extensions/jai_codec.jar, > /System/Library/Java/Extensions/jai_core.jar, > /System/Library/Java/Extensions/mlibwrapper_jai.jar, > /System/Library/Java/Extensions/MRJToolkit.jar, > /System/Library/Java/Extensions/QTJava.zip, > /System/Library/Java/Extensions/vecmath.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/dnsns.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/localedata.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunjce_provider.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunpkcs11.jar, > /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar, > /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar, > /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar, > /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar, > /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar, > /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar, > /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar, > /Users/esm/.m2/repository/edu/jhu/library/embargo/embargo-api/1.0.0-SNAPSHOT/embargo-api-1.0.0-SNAPSHOT.jar, > > /Users/esm/.m2/repository/commons-logging/commons-logging/1.1/commons-lo
[jira] Created: (NMAVEN-128) Document packaging and built-in lifecycle bindings
Document packaging and built-in lifecycle bindings -- Key: NMAVEN-128 URL: http://jira.codehaus.org/browse/NMAVEN-128 Project: NMaven Issue Type: Improvement Affects Versions: 0.14 (Unreleased) Reporter: Wendy Smoak We should document the available packaging options and built-in lifecycle bindings. Similar to: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Built-in_Lifecycle_Bindings Related thread: http://www.nabble.com/NMaven-packaging-and-lifecycle-bindings-td17328669.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (NMAVEN-127) Simple C# Archetype is missing a name
Simple C# Archetype is missing a name - Key: NMAVEN-127 URL: http://jira.codehaus.org/browse/NMAVEN-127 Project: NMaven Issue Type: Improvement Affects Versions: 0.14 (Unreleased) Environment: 0.14 branch + patches Reporter: Wendy Smoak Building a project created from the C# simple archetype results in: C:\Temp\NMaven.Sample>mvn install [INFO] Scanning for projects... [INFO] [INFO] Building Unnamed - NMaven:NMaven.Sample:library:1.0-SNAPSHOT [INFO]task-segment: [install] [INFO] Adding a element will eliminate the "Building Unnamed..." message. (Also check the other archetypes) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (NMAVEN-126) Unable to retrieve and use timestamped snapshots of plugins
Unable to retrieve and use timestamped snapshots of plugins --- Key: NMAVEN-126 URL: http://jira.codehaus.org/browse/NMAVEN-126 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Environment: 0.14 branch + patches Reporter: Wendy Smoak Attempting to build the C# quickstart project against a remote repo containing timestamped snapshots does not work. >mvn archetype:create ... -DarchetypeArtifactId=maven-archetype-dotnet-simple >... ... C:\Temp\NMaven.Sample>mvn install [INFO] Scanning for projects... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.dotnet.plugins:maven-compile-plugin Reason: Error getting POM for 'org.apache.maven.dotnet.plugins:maven-compile-plugin' from the repository: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata. org.apache.maven.dotnet.plugins:maven-compile-plugin:pom:0.14-20080521.120818-19 from the specified remote repositories: ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SCM-368) Windows path length limitations can be overcome by feeding an absolute path to SVN
[ http://jira.codehaus.org/browse/SCM-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed SCM-368. Resolution: Fixed New fix. Olivier can you verify it? > Windows path length limitations can be overcome by feeding an absolute path > to SVN > -- > > Key: SCM-368 > URL: http://jira.codehaus.org/browse/SCM-368 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-api >Affects Versions: 1.0 > Environment: Any Windows machine >Reporter: Kurt Tometich >Assignee: Emmanuel Venisse >Priority: Minor > Fix For: 1.1 > > > When calling Subversion with relative paths there is a limit of 255 > characters to the path length. If you call Subversion with an absolute path > that no longer applies and you now have access to 32K chars. I have tried > this myself and it does work. Try feeding SVN a path that is relative and is > over 255 chars. It will not be able to complete the transaction. Now, try > to the same path again only as an absolute path and it will successfully > complete the transaction. Here is a link to the forum where I found this > information: http://en-us.www.mozilla.com/en-US/firefox/2.0.0.4/firstrun/. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPIR-95) Better handling of HTML license documents
[
http://jira.codehaus.org/browse/MPIR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPIR-95.
---
Resolution: Won't Fix
You could add a license file in your project something like:
{noformat}
...
The MIT License
file://${basedir}/LICENSE.txt
repo
...
{noformat}
> Better handling of HTML license documents
> -
>
> Key: MPIR-95
> URL: http://jira.codehaus.org/browse/MPIR-95
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Components: license
>Affects Versions: 2.1
>Reporter: Martin von Gagern
>Priority: Minor
> Attachments: pom.xml
>
>
> I've got a document here specifying
> http://www.opensource.org/licenses/mit-license.php as its license. This is
> handles rather poorly by the generated license document, as the framework
> around the license text gets in the way and the heading levels of the license
> text don't fit. I can imagine several possible solutions to improve this
> situations:
> 1. Specify local file in pom. This makes it difficult to automatically handle
> licensing automatically, as only well known public URLs can be used to
> identify well known licenses, which won't work for local file names or
> private web sites.
> 2. Provide a way to specify appropriate local files for licenses without
> touching the url in the pom. This could take the form of some map parameter
> that associates license names with license documents.
> 3. Provide a way to simply not include any license text, only the link. This
> is the quickest solution.
> 4. Embed the license text as an iframe with an external source, so you only
> link and copy nothing.
> 5. Parse HTML and allow XPath selectors or something similar to extract the
> license content.
> When you do some better HTML parsing one day (maybe using
> org.htmlparser:htmlparser?), you might wish to adjust headline levels as
> well. Find the highest level headline that occurs in the extracted fragment,
> calculate an offset that places this one level below the license name
> headline printed by the plugin, and apply this offset to every headline in
> the fragment.
> If you decide for one of the solutions 2-4, I guess I could hack a quick
> patch to implement this. 5 is more work, of course.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPIR-94) Change optional label in dependencies site
[ http://jira.codehaus.org/browse/MPIR-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-94. --- Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.1 fixed in r659261, snapshot deployed > Change optional label in dependencies site > -- > > Key: MPIR-94 > URL: http://jira.codehaus.org/browse/MPIR-94 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies >Affects Versions: 2.0.1 >Reporter: Michael Osipov >Assignee: Vincent Siveton >Priority: Minor > Fix For: 2.1 > > > If you check the project dependencies page, the table says for an aoptional > dependency "(optional)". This is actually not really intuitive. A "yes" would > be much more help full or even more, let the user configure a term for both > states. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3560) unable to use plugins that exist in multiple repositories
[
http://jira.codehaus.org/browse/MNG-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135776#action_135776
]
Wendy Smoak commented on MNG-3560:
--
Maven 2.0.9 + this patch is working for me.
I know it's a bit hard to reproduce, but if you've got plugins split across
repositories (stable vs. sandbox) you're likely to see problems downloading
plugins.
Can someone please review and apply the patch (or raise any issues with it?)
> unable to use plugins that exist in multiple repositories
> -
>
> Key: MNG-3560
> URL: http://jira.codehaus.org/browse/MNG-3560
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 2.0.9
>Reporter: Maria Catherine Tan
> Attachments: MNG-3560-maven-artifact.patch
>
>
> I created two test cases using maven-2.0.9
> A. Here's the settings for my first test case which builds successfully using
> mvn site or mvn site -up
> 1. Created two remote repository
> - sandbox has maven-project-info-reports-plugin 2.0.1
> - corporate has maven-project-info-reports-plugin 2.0
> 2. No maven-project-info-reports-plugin in my local repository
> 3. Access to central repository is disabled
> 4. The order in my settings.xml for the plugin repositories is sandbox first
> before corporate
>
> sandbox
> http://localhost:9091/repository/sandbox
>
>
> corporate
> http://localhost:9091/repository/corporate
>
> Result:
> * downloaded maven-project-info-reports-plugin 2.0 pom in corporate
> * check maven-project-info-reports-plugin 2.0 jar in sandbox
> * downloaded maven-project-info-reports-plugin 2.0 jar in corporate
> {code}
> [EMAIL PROTECTED]:~/projects/testproject$ mvn site -up
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building testproject
> [INFO]task-segment: [site]
> [INFO]
>
> [INFO] artifact org.apache.maven.plugins:maven-project-info-reports-plugin:
> checking for updates from sandbox
> [INFO] artifact org.apache.maven.plugins:maven-project-info-reports-plugin:
> checking for updates from corporate
> [INFO] artifact org.apache.maven.plugins:maven-project-info-reports-plugin:
> checking for updates from central
> [WARNING] repository metadata for: 'artifact
> org.apache.maven.plugins:maven-project-info-reports-plugin' could not be
> retrieved from repository: central due to an error: Error transferring file
> [INFO] Repository 'central' will be blacklisted
> Downloading:
> http://localhost:9091/repository/corporate/org/apache/maven/plugins/maven-project-info-reports-plugin/2.0/maven-project-info-reports-plugin-2.0.pom
> 5K downloaded
> Downloading:
> http://localhost:9091/repository/sandbox/org/apache/maven/plugins/maven-project-info-reports-plugin/2.0/maven-project-info-reports-plugin-2.0.jar
> Downloading:
> http://localhost:9091/repository/corporate/org/apache/maven/plugins/maven-project-info-reports-plugin/2.0/maven-project-info-reports-plugin-2.0.jar
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] [site:site]
> [INFO] Generating "Source Repository" report.
> [INFO] Generating "Issue Tracking" report.
> [INFO] Generating "About" report.
> [INFO] Generating "Project License" report.
> [INFO] Generating "Project Summary" report.
> [INFO] Generating "Dependencies" report.
> [INFO] Generating "Continuous Integration" report.
> [INFO] Generating "Project Team" report.
> [INFO] Generating "Mailing Lists" report.
> [INFO]
>
> [INFO] BUILD SUCCESSFUL
> [INFO]
>
> {code}
> B. Here's the settings for my second test case which replicate this issue
> 1. Created two remote repository
> - sandbox has maven-project-info-reports-plugin 2.0.1
> - corporate has maven-project-info-reports-plugin 2.0
> 2. No maven-project-info-reports-plugin in my local repository
> 3. Access to central repository is disabled
> 4. The order in my settings.xml for the plugin repositories is corporate
> first before sandbox
>
> corporate
> http://localhost:9091/repository/corporate
>
>
> sandbox
> http://localhost:9091/repository/sandbox
>
> Result:
> * downloaded maven-project-info-reports-plugin 2.0 pom in sandbox which
> it did not find and never tries to check the corporate where the pom could be
> found
> * downloade
[jira] Closed: (MRELEASE-302) Test don't pass on windows due to encoding issues
[ http://jira.codehaus.org/browse/MRELEASE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MRELEASE-302. -- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.0-beta-8 Fixed in [r659241|http://svn.apache.org/viewvc?view=rev&revision=659241]. Code should never rely on the capabilities of the SCM, line terminators must simply be handled in all their flavors. > Test don't pass on windows due to encoding issues > - > > Key: MRELEASE-302 > URL: http://jira.codehaus.org/browse/MRELEASE-302 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-8 >Reporter: Carlos Sanchez >Assignee: Benjamin Bentmann >Priority: Critical > Fix For: 2.0-beta-8 > > Attachments: > org.apache.maven.shared.release.phase.CreateBackupPomsPhaseTest.txt, > org.apache.maven.shared.release.phase.GenerateReleasePomsPhaseTest.txt, > org.apache.maven.shared.release.phase.RewritePomsForDevelopmentPhaseTest.txt, > org.apache.maven.shared.release.phase.RewritePomsForReleasePhaseTest.txt > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-254) tests failed on windows
[
http://jira.codehaus.org/browse/MRELEASE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MRELEASE-254.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.0-beta-8
Fixed in [r659241|http://svn.apache.org/viewvc?view=rev&revision=659241].
This was indeed a line ending problem: Because of different line endings, the
{{content.indexOf()}} failed which caused the intro/outtro to be missed.
> tests failed on windows
> ---
>
> Key: MRELEASE-254
> URL: http://jira.codehaus.org/browse/MRELEASE-254
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Environment: windows + cygwin
>Reporter: Olivier Lamy
>Assignee: Benjamin Bentmann
> Fix For: 2.0-beta-8
>
> Attachments: build.log, MRELEASE-254,
> org.apache.maven.shared.release.phase.RewritePomsForDevelopmentPhaseTest.txt,
> output.txt
>
>
> Tests failed on windows due to Comparing files with String equals method.
> This patch compares xml content with using xmlunit.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3591) disable warning
[ http://jira.codehaus.org/browse/MNG-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3591. --- Resolution: Fixed Fix Version/s: 2.1-alpha-1 disabled until a 2.1 release is imminent. Since the feature is deprecated, it's important to warn users about it. However, since the 2.1 snapshots are being used in IDE support, it's important to avoid confusing the deprecations in the IDE support with those in the predominantly 2.0.x environment of the command line. > disable warning > - > > Key: MNG-3591 > URL: http://jira.codehaus.org/browse/MNG-3591 > Project: Maven 2 > Issue Type: Bug >Reporter: Eugene Kuleshov >Assignee: John Casey > Fix For: 2.1-alpha-1 > > > warning is very confusing for users who are using mvn > 2.0.x and 2.1 at the same time (i.e. IDE users). So it would be a good ide to > disable it at least until 2.1 is released. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPIR-86) Customizable Team list report
[ http://jira.codehaus.org/browse/MPIR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-86. --- Resolution: Duplicate > Customizable Team list report > - > > Key: MPIR-86 > URL: http://jira.codehaus.org/browse/MPIR-86 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: project-team >Reporter: Roberto Lo Giacco > > It would be nice and useful to allow for Team list report customization at > least in terms of which columns to display and which to hide. > In my experience the URL, Organization,Organization URL, Time Zone, Actual > Time (GMT) and Properties columns are pratically unused and eats space. > In an optimal view it would be practical to include only columns for which > there is at least a value in one of the rows, automatically excluding the > columns never valorized. > If you can redirect me and give some hints I can contribute myself the > correction. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MWAR-159) Filtering deployments descriptors (web.xml)
[ http://jira.codehaus.org/browse/MWAR-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MWAR-159. - Resolution: Fixed fix in rev 659214 > Filtering deployments descriptors (web.xml) > --- > > Key: MWAR-159 > URL: http://jira.codehaus.org/browse/MWAR-159 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.1-alpha-1 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.1-alpha-2 > > > to preserve backward compatibility this option will be off by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2068) Upload NeoDatis ODB
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135760#action_135760 ] Antonio Petrelli commented on MAVENUPLOAD-2068: --- Big thanks, Carlos! > Upload NeoDatis ODB > --- > > Key: MAVENUPLOAD-2068 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2068 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Antonio Petrelli >Assignee: Carlos Sanchez > Attachments: neodatis-odb-bundle.jar > > > Please upload NeoDatis ODB, attached with this issue. > NeoDatis ODB is a very simple Object Oriented Database for the Java platform. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (NMAVEN-125) NUnit dependency should be in test scope
NUnit dependency should be in test scope
Key: NMAVEN-125
URL: http://jira.codehaus.org/browse/NMAVEN-125
Project: NMaven
Issue Type: Bug
Affects Versions: 0.14 (Unreleased)
Environment: NNmaven 0.14 branch + patches
Reporter: Wendy Smoak
Priority: Minor
In a project created from maven-archetype-dotnet-simple, the NUnit dependency
is not in test scope.
It should be:
{noformat}
NUnit
NUnit.Framework
2.2.8.0
library
test < add this line
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MANTRUN-20) Antrun plugin defaults to using jre classpath instead of jdk
[ http://jira.codehaus.org/browse/MANTRUN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135753#action_135753 ] Tim Fliss commented on MANTRUN-20: -- I agree. Normal doesn't mean correct. referencing tools.jar seems to be the workaround (an unsatisfactory one if you need to build on macs because of all the extra profile settings). If java.home pointed at the actual java.home set by the user, and would find tools.jar on its own. In any case a better explanation would help. > Antrun plugin defaults to using jre classpath instead of jdk > > > Key: MANTRUN-20 > URL: http://jira.codehaus.org/browse/MANTRUN-20 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Reporter: ruel loehr >Assignee: Brett Porter > > When executing ant tasks via the antrun plugin, maven reconciles them with a > jre classpath. You can verify this by running the antrun plugin with the > following task: > > The solution I can see is to add a plugin dependency on the antrun plugin > which resolves to the tools.jar, however another bug prevents this from > working in anything but top level projects. Hence, the antrun plugin cannot > be used for any compilation purposes (javac, rmic) for child projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2045) Upload SNMP4J 1.9.1e
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2045. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload SNMP4J 1.9.1e > > > Key: MAVENUPLOAD-2045 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2045 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Paul Donohue >Assignee: Carlos Sanchez > > http://www.PaulSD.com/snmp4j-1.9.1e-bundle.jar > http://www.snmp4j.org/ > I AM NOT an SNMP4J developer. I asked about updating the maven repo on the > SNMP4J mailing list and received no response, so I assume they are ok with me > requesting an update to the maven repo. 1.9.1e is the latest release. > Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2058) Please upload spring-json-1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2058. --- Assignee: Carlos Sanchez Resolution: Fixed > Please upload spring-json-1.0 > - > > Key: MAVENUPLOAD-2058 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2058 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Kai Ulrich >Assignee: Carlos Sanchez > Attachments: spring-json-1.0-bundle-new-pom.jar, > spring-json-1.0-bundle.jar > > > Spring Json-View adds JavaScript Object Notation (json) support to > Spring-MVC. It is deaply integrated into the spring mvc-module and can be > used with all kind standart-controllers. > Im the leaddeveloper and my alternative email is [EMAIL PROTECTED] > thanks > kai -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2073) Clover2.3.1 Maven1 Plugin upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2073. --- Assignee: Carlos Sanchez Resolution: Fixed > Clover2.3.1 Maven1 Plugin upload request > > > Key: MAVENUPLOAD-2073 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2073 > Project: maven-upload-requests > Issue Type: Task >Reporter: Nick Pellow >Assignee: Carlos Sanchez > > We have just released version 2.3.1 of Clover and the Maven1 Clover plugin. > This fixes a problem when running Clover under jdk 1.4. > Could you please deploy this bundle to the maven central repository. > Kind Regards, > Nick Pellow -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2074) Clover2.3.1 artifact upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2074. --- Assignee: Carlos Sanchez Resolution: Fixed > Clover2.3.1 artifact upload > --- > > Key: MAVENUPLOAD-2074 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2074 > Project: maven-upload-requests > Issue Type: Task >Reporter: Nick Pellow >Assignee: Carlos Sanchez > > This bundle contains the Clover 2.3.1 core classes. The Maven Clover 2.3.1 > plugin depends on this. > Could you please upload this to your maven1 repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2021) DataCleaner-core 1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2021. --- Assignee: Carlos Sanchez Resolution: Fixed > DataCleaner-core 1.0 > > > Key: MAVENUPLOAD-2021 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2021 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Kasper Sørensen >Assignee: Carlos Sanchez > > I'm the founder and main developer of DataCleaner. Please upload > PS: The website will be down a couple of hours for maintenance tomorrow, so > if you're unlucky try a bit later. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2059) Upload FreeMarker 2.3.13
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2059. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload FreeMarker 2.3.13 > > > Key: MAVENUPLOAD-2059 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2059 > Project: maven-upload-requests > Issue Type: Task >Reporter: Mirko Nasato >Assignee: Carlos Sanchez > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2072) Upload FCKeditor.Java 2.4. Beta 1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2072. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload FCKeditor.Java 2.4. Beta 1 > - > > Key: MAVENUPLOAD-2072 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2072 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Michael Osipov >Assignee: Carlos Sanchez > > "net.fckeditor","rsync://java.fckeditor.net/m2repo","rsync","Michael > Osipov","[EMAIL PROTECTED]",, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2070) rsync_ssh request for caelum-stella.sourceforge.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2070. --- Assignee: Carlos Sanchez Resolution: Fixed > rsync_ssh request for caelum-stella.sourceforge.net > --- > > Key: MAVENUPLOAD-2070 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2070 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Cauê Haucke Porta Guerra >Assignee: Carlos Sanchez > > "net.sf.caelum-stella","[EMAIL > PROTECTED]:/home/groups/c/ca/caelum-stella/htdocs/m2repo","rsync_ssh","Caue > Guerra","[EMAIL PROTECTED]",, > Project page generated by maven hosted at project domain: > http://stella.caelum.com.br/dev/team-list.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2071) rsync_ssh request for seleniumdsl.sourceforge.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2071. --- Assignee: Carlos Sanchez Resolution: Fixed > rsync_ssh request for seleniumdsl.sourceforge.net > - > > Key: MAVENUPLOAD-2071 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2071 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Cauê Haucke Porta Guerra >Assignee: Carlos Sanchez > > "net.sf.seleniumdsl","[EMAIL > PROTECTED]:/home/groups/s/se/seleniumdsl/htdocs/m2repo","rsync_ssh","Caue > Guerra","[EMAIL PROTECTED]",, > Project page generated by maven hosted at project domain: > http://seleniumdsl.sourceforge.net/team-list.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2069) upload JPED repository to maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2069. --- Assignee: Carlos Sanchez Resolution: Fixed > upload JPED repository to maven repository > -- > > Key: MAVENUPLOAD-2069 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2069 > Project: maven-upload-requests > Issue Type: Wish >Reporter: David Delbecq >Assignee: Carlos Sanchez > > Please sync jped internal release repository with maven central repository > "net.sf.jped","[EMAIL > PROTECTED]:/home/groups/j/jp/jped/maven2/","rsync_ssh","David > Delbecq","[EMAIL PROTECTED]",, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2068) Upload NeoDatis ODB
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2068. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload NeoDatis ODB > --- > > Key: MAVENUPLOAD-2068 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2068 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Antonio Petrelli >Assignee: Carlos Sanchez > Attachments: neodatis-odb-bundle.jar > > > Please upload NeoDatis ODB, attached with this issue. > NeoDatis ODB is a very simple Object Oriented Database for the Java platform. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2067) JasperReports 3.0.0 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2067. --- Assignee: Carlos Sanchez Resolution: Fixed > JasperReports 3.0.0 upload > -- > > Key: MAVENUPLOAD-2067 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2067 > Project: maven-upload-requests > Issue Type: Task >Reporter: Teodor Danciu >Assignee: Carlos Sanchez > > http://jasperreports.sf.net/maven/jasperreports-3.0.0-bundle.jar > http://sourceforge.net/projects/jasperreports > http://sourceforge.net/project/memberlist.php?group_id=36382 > Open Source Reporting Engine -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2066) rsync EasyMock to maven central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2066. --- Assignee: Carlos Sanchez Resolution: Fixed > rsync EasyMock to maven central repository > -- > > Key: MAVENUPLOAD-2066 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2066 > Project: maven-upload-requests > Issue Type: Task >Reporter: Henri Tremblay >Assignee: Carlos Sanchez > > Please configure the rsync with the easymock repository. > The rsync line: > "org.easymock","[EMAIL > PROTECTED]:/home/groups/e/ea/easymock/htdocs/maven/repository","rsync_ssh","Henri > Tremblay","[EMAIL PROTECTED]",, > The question might be dumb but do I need any particular rights on the > repository? (a+r?) > And if I remove something from my repo, will it disappear from the central > repository? > Lastly, can I synchronise projects with another group id? (I'm thinking about > Objenesis here) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2040) rsync_ssh request for domdrides.sourceforge.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2040. --- Assignee: Carlos Sanchez Resolution: Fixed > rsync_ssh request for domdrides.sourceforge.net > --- > > Key: MAVENUPLOAD-2040 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2040 > Project: maven-upload-requests > Issue Type: Wish >Reporter: James Carman >Assignee: Carlos Sanchez > > "org.domdrides","[EMAIL > PROTECTED]:/home/groups/d/do/domdrides/htdocs/m2repo/releases","rsync_ssh","James > Carman","[EMAIL PROTECTED]",, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2066) rsync EasyMock to maven central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135745#action_135745 ] Carlos Sanchez commented on MAVENUPLOAD-2066: - > The question might be dumb but do I need any particular rights on the > repository? (a+r?) world readable > And if I remove something from my repo, will it disappear from the central > repository? no > Lastly, can I synchronise projects with another group id? (I'm thinking about > Objenesis here) yes, if they dont do it already > rsync EasyMock to maven central repository > -- > > Key: MAVENUPLOAD-2066 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2066 > Project: maven-upload-requests > Issue Type: Task >Reporter: Henri Tremblay > > Please configure the rsync with the easymock repository. > The rsync line: > "org.easymock","[EMAIL > PROTECTED]:/home/groups/e/ea/easymock/htdocs/maven/repository","rsync_ssh","Henri > Tremblay","[EMAIL PROTECTED]",, > The question might be dumb but do I need any particular rights on the > repository? (a+r?) > And if I remove something from my repo, will it disappear from the central > repository? > Lastly, can I synchronise projects with another group id? (I'm thinking about > Objenesis here) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3592) provide mechanism to serialize/deserialize MavenProject
provide mechanism to serialize/deserialize MavenProject --- Key: MNG-3592 URL: http://jira.codehaus.org/browse/MNG-3592 Project: Maven 2 Issue Type: New Feature Reporter: Eugene Kuleshov When working with embedded Maven it would be useful to be able to persist MavenProject instances (using some form of serialization), so we could restore it without triggering full project resolution. One example of that is a form of persistent caching that will be very useful in the IDE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2065) Flying Saucer xhtmlrenderer R8pre2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2065. --- Assignee: Carlos Sanchez Resolution: Fixed > Flying Saucer xhtmlrenderer R8pre2 > -- > > Key: MAVENUPLOAD-2065 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2065 > Project: maven-upload-requests > Issue Type: Task >Reporter: fabrizio giustina >Assignee: Carlos Sanchez > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3591) disable warning
[ http://jira.codehaus.org/browse/MNG-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135744#action_135744 ] Milos Kleint commented on MNG-3591: --- FYI, I'm recognizing the line in the events sent by the embedded build in netbeans and filter it out for the same reason. > disable warning > - > > Key: MNG-3591 > URL: http://jira.codehaus.org/browse/MNG-3591 > Project: Maven 2 > Issue Type: Bug >Reporter: Eugene Kuleshov >Assignee: John Casey > > warning is very confusing for users who are using mvn > 2.0.x and 2.1 at the same time (i.e. IDE users). So it would be a good ide to > disable it at least until 2.1 is released. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3591) disable warning
disable warning - Key: MNG-3591 URL: http://jira.codehaus.org/browse/MNG-3591 Project: Maven 2 Issue Type: Bug Reporter: Eugene Kuleshov warning is very confusing for users who are using mvn 2.0.x and 2.1 at the same time (i.e. IDE users). So it would be a good ide to disable it at least until 2.1 is released. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects
[ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135723#action_135723 ] Robin Custers commented on MRELEASE-261: does the 2.0-beta-8-SNAPSHOT version already includes this fix? If not how can i use the patched version? I tried apply your workaround to the 2.0-beta-8-SNAPSHOT but got the following error: [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [clean, verify] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot execute mojo: clean. It requires a project with an existing pom.xml, but the build is not using one. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Thu May 22 17:04:49 CEST 2008 [INFO] Final Memory: 1M/3M [INFO] [INFO] Tnx - Robin > release:prepare shouls support flat directory multimodule projects > -- > > Key: MRELEASE-261 > URL: http://jira.codehaus.org/browse/MRELEASE-261 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Environment: linux / maven2 / svn >Reporter: [EMAIL PROTECTED] > Attachments: PrepareReleaseMojo.patch > > > What I mean by flat file structure firstly. > parent/pom.xml > module1/pom.xml > module2/pom.xml > . > . > . > module15/pom.xml > the parent references the modules like so > > ../module1 > ../module2 > . > . > . > ../module15 > > When i release:prepare only the parent project is tagged the modules > projects versions are incremented etc but the modules are not tagged in svn. > I use this structure as i use eclipse as my IDE. > I would love to see a fix for the issue marked as closed here > http://jira.codehaus.org/browse/MRELEASE-138. I am currenrly tagging by hand > each submodule of the projects but it would be so nice to have the release > plugin do this for me. > forgive my english. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MARTIFACT-17) Add generics details to collections
[ http://jira.codehaus.org/browse/MARTIFACT-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MARTIFACT-17. -- Resolution: Fixed Patch applied. > Add generics details to collections > --- > > Key: MARTIFACT-17 > URL: http://jira.codehaus.org/browse/MARTIFACT-17 > Project: Maven Artifact > Issue Type: Improvement >Reporter: Jason Dillon >Assignee: Jason van Zyl > Attachments: MARTIFACT-17-2.diff, MARTIFACT-17.diff > > > Also adds some use of java5 for bits and such. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCOMPILER-75) Add apt support for Java 6
[
http://jira.codehaus.org/browse/MCOMPILER-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson updated MCOMPILER-75:
-
Description:
Apt (Annotation Processing Tool) was merged into javac in Java 6. The compiler
plugin should support this new functionality, which means supporting the
following new arguments:
{noformat}
-proc:{none,only} Control whether annotation processing and/or
compilation is done.
-processor [,,...]Names of the annotation processors
to run; bypasses default discovery process
-processorpath Specify where to find annotation processors
-s Specify where to place generated source files
-implicit:{none,class} Specify whether or not to generate class files for
implicitly referenced files
-Akey[=value] Options to pass to annotation processors
{noformat}
Note that this should supersede the Apt Maven Plugin at Mojo by encompassing
all of its functionality:
http://mojo.codehaus.org/apt-maven-plugin/index.html
was:
Apt (Annotation Processing Tool) was merged into javac in JDK6. The compiler
plugin should support this new functionality, which means supporting the
following new arguments:
{noformat}
-proc:{none,only} Control whether annotation processing and/or
compilation is done.
-processor [,,...]Names of the annotation processors
to run; bypasses default discovery process
-processorpath Specify where to find annotation processors
-s Specify where to place generated source files
-implicit:{none,class} Specify whether or not to generate class files for
implicitly referenced files
-Akey[=value] Options to pass to annotation processors
{noformat}
Note that this should supersede the Apt Maven Plugin at Mojo by encompassing
all of its functionality:
http://mojo.codehaus.org/apt-maven-plugin/index.html
Summary: Add apt support for Java 6 (was: Add apt support for JDK6)
> Add apt support for Java 6
> --
>
> Key: MCOMPILER-75
> URL: http://jira.codehaus.org/browse/MCOMPILER-75
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
>Affects Versions: 2.0.2
>Reporter: Mark Hobson
>
> Apt (Annotation Processing Tool) was merged into javac in Java 6. The
> compiler plugin should support this new functionality, which means supporting
> the following new arguments:
> {noformat}
> -proc:{none,only} Control whether annotation processing and/or
> compilation is done.
> -processor [,,...]Names of the annotation
> processors to run; bypasses default discovery process
> -processorpath Specify where to find annotation processors
> -s Specify where to place generated source files
> -implicit:{none,class} Specify whether or not to generate class files
> for implicitly referenced files
> -Akey[=value] Options to pass to annotation processors
> {noformat}
> Note that this should supersede the Apt Maven Plugin at Mojo by encompassing
> all of its functionality:
> http://mojo.codehaus.org/apt-maven-plugin/index.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCOMPILER-75) Add apt support for JDK6
Add apt support for JDK6
Key: MCOMPILER-75
URL: http://jira.codehaus.org/browse/MCOMPILER-75
Project: Maven 2.x Compiler Plugin
Issue Type: New Feature
Affects Versions: 2.0.2
Reporter: Mark Hobson
Apt (Annotation Processing Tool) was merged into javac in JDK6. The compiler
plugin should support this new functionality, which means supporting the
following new arguments:
{noformat}
-proc:{none,only} Control whether annotation processing and/or
compilation is done.
-processor [,,...]Names of the annotation processors
to run; bypasses default discovery process
-processorpath Specify where to find annotation processors
-s Specify where to place generated source files
-implicit:{none,class} Specify whether or not to generate class files for
implicitly referenced files
-Akey[=value] Options to pass to annotation processors
{noformat}
Note that this should supersede the Apt Maven Plugin at Mojo by encompassing
all of its functionality:
http://mojo.codehaus.org/apt-maven-plugin/index.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2058) Please upload spring-json-1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135710#action_135710 ] Kai Ulrich commented on MAVENUPLOAD-2058: - for download use spring-json-1.0-bundle-new-pom.jar (see Attachments) or better the Bundle URL http://spring-json.sourceforge.net/downloads/spring-json-1.0-bundle.jar > Please upload spring-json-1.0 > - > > Key: MAVENUPLOAD-2058 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2058 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Kai Ulrich > Attachments: spring-json-1.0-bundle-new-pom.jar, > spring-json-1.0-bundle.jar > > > Spring Json-View adds JavaScript Object Notation (json) support to > Spring-MVC. It is deaply integrated into the spring mvc-module and can be > used with all kind standart-controllers. > Im the leaddeveloper and my alternative email is [EMAIL PROTECTED] > thanks > kai -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MAVENUPLOAD-2058) Please upload spring-json-1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Ulrich updated MAVENUPLOAD-2058: Attachment: spring-json-1.0-bundle-new-pom.jar > Please upload spring-json-1.0 > - > > Key: MAVENUPLOAD-2058 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2058 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Kai Ulrich > Attachments: spring-json-1.0-bundle-new-pom.jar, > spring-json-1.0-bundle.jar > > > Spring Json-View adds JavaScript Object Notation (json) support to > Spring-MVC. It is deaply integrated into the spring mvc-module and can be > used with all kind standart-controllers. > Im the leaddeveloper and my alternative email is [EMAIL PROTECTED] > thanks > kai -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3580) FATAL ERROR and NPE on start
[
http://jira.codehaus.org/browse/MNG-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135709#action_135709
]
Benjamin Bentmann commented on MNG-3580:
bq. but no clue for IBM
My code snippet was specially crafted to trigger the faulty code path in
Harmony. There might just be a similar bug in the IBM JRE that simply is not
revealed by the test snippet. As far as I can tell after some debugging through
Maven, Maven itself is not inserting nulls into the plugin list so somebody
else seems to do... If you really want to know, you could simply set a break
point on ModelUtils.java:243 and verify the {{results}} list is properly
populated by {{ArrayList.addAll()}}.
> FATAL ERROR and NPE on start
>
>
> Key: MNG-3580
> URL: http://jira.codehaus.org/browse/MNG-3580
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.9
> Environment: Linux iitm50ws1106 2.6.25.3-2-default #1 SMP 2008-05-10
> 07:46:36 +0200 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pxa6460sr1-20080416_01(SR1))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64
> jvmxa6460-20080415_18762 (JIT enabled, AOT enabled)
> J9VM - 20080415_018762_LHdSMr
> JIT - r9_20080415_1520
> GC - 20080415_AA)
> JCL - 20080412_01
>Reporter: Erik Putrycz
> Attachments: maven.log, MNG-3580.patch
>
>
> Any mvn command does give me the following error message
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Business Rules Extractor
> [INFO] Business Rules Extractor core functions
> [INFO] COBOL Parser and ANTLR Tools
> [INFO] Business Rules Extractor data model
> [INFO] Documentation Extractor module
> [INFO] Extractor module
> [INFO] Business Rules Navigator
> WAGON_VERSION: 1.0-beta-2
> [INFO]
>
> [INFO] Building Business Rules Extractor
> [INFO]task-segment: [install]
> [INFO]
>
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.project.ModelUtils.mergePluginLists(ModelUtils.java:164)
> at
> org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleBuildInheritance(DefaultModelInheritanceAssembler.java:366)
> at
> org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleModelInheritance(DefaultModelInheritanceAssembler.java:168)
> at
> org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleModelInheritance(DefaultModelInheritanceAssembler.java:61)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:852)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:253)
> at
> org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:265)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:197)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1033)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:997)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.Nat
[jira] Commented: (MNG-3580) FATAL ERROR and NPE on start
[
http://jira.codehaus.org/browse/MNG-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135706#action_135706
]
Vincent Siveton commented on MNG-3580:
--
FYI on IBM, the result is
{noformat}
http://www.ibm.com/
11
[i, h, g, f, e, d, 1, 2, c, b, a]
false
{noformat}
So, we found an issue in Harmony (HARMONY-5839) but no clue for IBM
I agree with you that it is the contract of the vendor to respect the JDK.
> FATAL ERROR and NPE on start
>
>
> Key: MNG-3580
> URL: http://jira.codehaus.org/browse/MNG-3580
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.9
> Environment: Linux iitm50ws1106 2.6.25.3-2-default #1 SMP 2008-05-10
> 07:46:36 +0200 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pxa6460sr1-20080416_01(SR1))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64
> jvmxa6460-20080415_18762 (JIT enabled, AOT enabled)
> J9VM - 20080415_018762_LHdSMr
> JIT - r9_20080415_1520
> GC - 20080415_AA)
> JCL - 20080412_01
>Reporter: Erik Putrycz
> Attachments: maven.log, MNG-3580.patch
>
>
> Any mvn command does give me the following error message
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Business Rules Extractor
> [INFO] Business Rules Extractor core functions
> [INFO] COBOL Parser and ANTLR Tools
> [INFO] Business Rules Extractor data model
> [INFO] Documentation Extractor module
> [INFO] Extractor module
> [INFO] Business Rules Navigator
> WAGON_VERSION: 1.0-beta-2
> [INFO]
>
> [INFO] Building Business Rules Extractor
> [INFO]task-segment: [install]
> [INFO]
>
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.project.ModelUtils.mergePluginLists(ModelUtils.java:164)
> at
> org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleBuildInheritance(DefaultModelInheritanceAssembler.java:366)
> at
> org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleModelInheritance(DefaultModelInheritanceAssembler.java:168)
> at
> org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleModelInheritance(DefaultModelInheritanceAssembler.java:61)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:852)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:253)
> at
> org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:265)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:197)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1033)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:997)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:59)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:39)
> at java.lang.reflect.Method.invoke(Method.java:612)
> at org.codehaus.classworlds.Launc
[jira] Commented: (MNG-3580) FATAL ERROR and NPE on start
[
http://jira.codehaus.org/browse/MNG-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135705#action_135705
]
Benjamin Bentmann commented on MNG-3580:
bq. but you forgot that JDK impl is vendor specific.
The terms "implementation" and "vendor specific" are inheritly related, that's
no news. My concern was that besides some vendor-specific differences under the
hood, *every* JRE impl must obey the contracts imposed by the API.
After some investigation, the problem boils down to a JRE bug just like Erik
assumed, i.e. the {{null}} value should never appear in the plugin list
iterated by Maven and it is not Maven's fault that it does. Take the following
code snippet:
{code:java}
Collection coll = Arrays.asList( new String[] { "1", "2" } );
List list = new ArrayList();
list.add( "a" );
list.add( 0, "b" );
list.add( 0, "c" );
list.add( 0, "d" );
list.add( 0, "e" );
list.add( 0, "f" );
list.add( 0, "g" );
list.add( 0, "h" );
list.add( 0, "i" );
list.addAll( 6, coll );
System.out.println( System.getProperty( "java.vendor.url" ) );
System.out.println( list.size() );
System.out.println( list );
System.out.println( list.contains( null ) );
{code}
On a Sun JDK the following output is observed:
{noformat}
http://java.sun.com/
11
[i, h, g, f, e, d, 1, 2, c, b, a]
false
{noformat}
In contrast, on harmony-jdk-629320 I observed
{noformat}
http://harmony.apache.org
12
[i, h, g, f, e, d, 1, 2, d, c, b, null]
true
{noformat}
which is just incorrect.
Facit: Here is nothing to fix in Maven. I wouldn't ever consider a workaround
since this would require to review *all* code spots that use {{ArrayList}} and
not just the one class {{ModelUtils}} where the JRE bug manifested itself for
the first time. The JRE vendor is responsible to fix this.
> FATAL ERROR and NPE on start
>
>
> Key: MNG-3580
> URL: http://jira.codehaus.org/browse/MNG-3580
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.9
> Environment: Linux iitm50ws1106 2.6.25.3-2-default #1 SMP 2008-05-10
> 07:46:36 +0200 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pxa6460sr1-20080416_01(SR1))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64
> jvmxa6460-20080415_18762 (JIT enabled, AOT enabled)
> J9VM - 20080415_018762_LHdSMr
> JIT - r9_20080415_1520
> GC - 20080415_AA)
> JCL - 20080412_01
>Reporter: Erik Putrycz
> Attachments: maven.log, MNG-3580.patch
>
>
> Any mvn command does give me the following error message
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Business Rules Extractor
> [INFO] Business Rules Extractor core functions
> [INFO] COBOL Parser and ANTLR Tools
> [INFO] Business Rules Extractor data model
> [INFO] Documentation Extractor module
> [INFO] Extractor module
> [INFO] Business Rules Navigator
> WAGON_VERSION: 1.0-beta-2
> [INFO]
>
> [INFO] Building Business Rules Extractor
> [INFO]task-segment: [install]
> [INFO]
>
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.project.ModelUtils.mergePluginLists(ModelUtils.java:164)
> at
> org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleBuildInheritance(DefaultModelInheritanceAssembler.java:366)
> at
> org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleModelInheritance(DefaultModelInheritanceAssembler.java:168)
> at
> org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleModelInheritance(DefaultModelInheritanceAssembler.java:61)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:852)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:253)
> at
> org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:265)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:197)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecy
[jira] Closed: (WAGON-213) Make the build be terse by default using latest surefire plugin
[ http://jira.codehaus.org/browse/WAGON-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-213. -- Resolution: Fixed Fix Version/s: 1.0-beta-3 > Make the build be terse by default using latest surefire plugin > --- > > Key: WAGON-213 > URL: http://jira.codehaus.org/browse/WAGON-213 > Project: Maven Wagon > Issue Type: Improvement >Reporter: Jason Dillon > Fix For: 1.0-beta-3 > > Attachments: WAGON-213 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (WAGON-212) Make FileWagonTest deterministic
[
http://jira.codehaus.org/browse/WAGON-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed WAGON-212.
--
Assignee: Brett Porter
Resolution: Fixed
Fix Version/s: 1.0-beta-3
> Make FileWagonTest deterministic
>
>
> Key: WAGON-212
> URL: http://jira.codehaus.org/browse/WAGON-212
> Project: Maven Wagon
> Issue Type: Task
> Components: wagon-file
>Affects Versions: 1.x
> Environment: WinXP, Sun JDK 1.6.0_04, Maven 2.0.9
>Reporter: Benjamin Bentmann
>Assignee: Brett Porter
> Fix For: 1.0-beta-3
>
> Attachments: org.apache.maven.wagon.providers.file.FileWagonTest.txt
>
>
> On a random basis, I observe the attached test failure
> {noformat}
> Failed tests:
> testWagon(org.apache.maven.wagon.providers.file.FileWagonTest)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2058) Please upload spring-json-1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135688#action_135688 ] Kai Ulrich commented on MAVENUPLOAD-2058: - OK, the pom is changed. The groupid now is net.sf.spring-json > Please upload spring-json-1.0 > - > > Key: MAVENUPLOAD-2058 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2058 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Kai Ulrich > Attachments: spring-json-1.0-bundle.jar > > > Spring Json-View adds JavaScript Object Notation (json) support to > Spring-MVC. It is deaply integrated into the spring mvc-module and can be > used with all kind standart-controllers. > Im the leaddeveloper and my alternative email is [EMAIL PROTECTED] > thanks > kai -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
