[jira] Commented: (MNG-2727) Fix Logging in threadsafe components
[ http://jira.codehaus.org/browse/MNG-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240741#action_240741 ] Brett Porter commented on MNG-2727: --- since the switch to Guice happened, is there anything still left to do here, or was it taken care of as suggested in the last comment? > Fix Logging in threadsafe components > > > Key: MNG-2727 > URL: http://jira.codehaus.org/browse/MNG-2727 > Project: Maven 2 & 3 > Issue Type: Task > Components: Embedding >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.x / Backlog > > -- 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-2006) Module SCM URL is resolved as [...]/parent/module regardless of relativePath
[ http://jira.codehaus.org/browse/MNG-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240742#action_240742 ] Florian Brunner commented on MNG-2006: -- I have similar issues. My project layout looks like this: PROJECT PROJECT/pom.xml (multi module project) PROJECT/parent PROJECT/parent/pom.xml PROJECT/module PROJECT/module/pom.xml This layout allows to build the parent POM without building its children and still support: cd PROJECT mvn clean install to build everything. PROJECT/parent/pom.xml is the parent of PROJECT/pom.xml and PROJECT/module/pom.xml > Module SCM URL is resolved as [...]/parent/module regardless of relativePath > > > Key: MNG-2006 > URL: http://jira.codehaus.org/browse/MNG-2006 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 2.0.2 > Environment: Maven 2.0.2 > Continuum 1.0.2 with maven-scm-*-1.0-beta-3-20060115.041342-*.jar >Reporter: Yann Le Du >Assignee: John Casey >Priority: Blocker > Fix For: 2.0.3 > > > Quoting Emmanuel Venisse from user list : > Ok, it's a bug in > http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/inheritance/DefaultModelInheritanceAssembler.java?rev=306518&view=markup > in assembleScmInheritance method. > This method append parent scm connection url and artifactId without look at > relativePath. > For detailed description see > http://www.nabble.com/-m2-Multiprojects-and-inherited-SCM-URLs-t951105.html > Project structure : > PROJECT > PROJECT/parent > PROJECT/parent/pom.xml > PROJECT/module > PROJECT/module/pom.xml > parent/pom.xml : > scm:svn:svn://host/PROJECT/parent/ > ../module > module/pom.xml : > ../parent/pom.xml > When I add module in Continuum, its url is resolved as : > scm:svn:svn://host/PROJECT/parent/module -- 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: (ARCHETYPE-326) fail on mvn install with a archetype created from create-from-project command
[
http://jira.codehaus.org/browse/ARCHETYPE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed ARCHETYPE-326.
---
Resolution: Fixed
Assignee: Herve Boutemy
fixed in r1026618
> fail on mvn install with a archetype created from create-from-project command
> -
>
> Key: ARCHETYPE-326
> URL: http://jira.codehaus.org/browse/ARCHETYPE-326
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 2.0-alpha-5
> Environment: Archetype plugin 2.0-alpha-6,
> OS name: "windows 2003" version: "5.2" arch: "x86" Family: "windows" , maven
> 2.2.1 (r801777; 2009-08-06 21:16:01+0200) , jdk 1.6.0_20
>Reporter: eric worth
>Assignee: Herve Boutemy
> Fix For: 2.0
>
>
> Creatin archetype form my projects was working 2 days ago, now it is broken ^^
> Try to create a project "foo" with "mvn archetype:generate",
> choose 16 for exemple, and follow documentation steps :
> - "mvn archetype:create-from-project"
> - cd target/generated-sources/archetype/
> - mvn install
> stack trace :
> {noformat}
> [INFO] [archetype:integration-test {execution: default-integration-test}]
> F:\dev\tmp\test\foo\target\generated-sources\archetype\target\test-classes\projects\basic\archetype.properties
> [ERROR] Archetype fr.mycompany.foo:foo-archetype:1.0-SNAPSHOT is not
> configured
> Property archetype.goals is missing.
> org.apache.maven.archetype.exception.ArchetypeNotConfigured: Archetype
> fr.mycompany.foo:foo-archetype:1.0-SNAPSHOT is not configured
> Property archetype.goals is missing.
> at
> org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:127)
> at
> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136)
> at
> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106)
> at
> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149)
> at
> org.apache.maven.archetype.mojos.IntegrationTestMojo.processIntegrationTest(IntegrationTestMojo.java:215)
> at
> org.apache.maven.archetype.mojos.IntegrationTestMojo.execute(IntegrationTestMojo.java:92)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> 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)
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Test basic failed
> [Ljava.lang.StackTraceElement;@864e43
> org.apache.maven.archetype.exception.ArchetypeNotConfigured: Archetype
> fr.mycompany.foo:foo-archetype:1.0-SNAPSHOT is not configured
> Property archetype.goals is missing.{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
-
Fo
[jira] Updated: (ARCHETYPE-322) archetype:generate throws "Too many open files" error
[
http://jira.codehaus.org/browse/ARCHETYPE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated ARCHETYPE-322:
Description:
mvn archetype:generate throws java.io.FileNotFoundException (Too many open
files) when I try to generate application from archetype containing more files
than system limit.
I've attached patch but I'm not sure if it's the best place to close files.
{noformat}[ERROR] java.io.FileNotFoundException:
/tmp/testartifact/src/main/webapp/css/test146.css (Too many open files)
org.apache.maven.archetype.exception.ArchetypeGenerationFailure:
java.io.FileNotFoundException:
/tmp/testartifact/src/main/webapp/css/test146.css (Too many open files)
at
org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:215)
at
org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136)
at
org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106)
at
org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149)
at
org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:209)
at
org.apache.maven.archetype.DefaultArchetypeManager.generateProjectFromArchetype(DefaultArchetypeManager.java:71)
at
org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:190)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
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){noformat}
was:
mvn archetype:generate throws java.io.FileNotFoundException (Too many open
files) when I try to generate application from archetype containing more files
than system limit.
I've attached patch but I'm not sure if it's the best place to close files.
[ERROR] java.io.FileNotFoundException:
/tmp/testartifact/src/main/webapp/css/test146.css (Too many open files)
org.apache.maven.archetype.exception.ArchetypeGenerationFailure:
java.io.FileNotFoundException:
/tmp/testartifact/src/main/webapp/css/test146.css (Too many open files)
at
org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:215)
at
org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136)
at
org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106)
at
org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149)
at
org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:209)
at
org.apache.maven.archetype.DefaultArchetypeManager.generateProjectFromArchetype(DefaultArchetypeManager.java:71)
at
org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:190)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.Defa
[jira] Updated: (ARCHETYPE-273) add goal to import remote archetype catalog into local catalog
[
http://jira.codehaus.org/browse/ARCHETYPE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated ARCHETYPE-273:
Description:
If I've just published a new archetype, I need to be able to provide the
developer with a command that allows them to "educate" their local catalog
about the new archetypes that area available. Currently, it's possible to
specify an archetype catalog for a single run of the generate goal:
{noformat}mvn archetype:generate
-DarchetypeCatalog=http://example.com/maven2{noformat}
But the catalog is transient. Those entries are not "remembered". The next time
I run the generate goal...
{noformat}mvn archetype:generate{noformat}
...the archetypes in the catalog provided in the previous command are not
offered as options.
This is especially problematic when using an IDE to create a new Maven project,
because the mechanism for providing an archetype catalog differs in each IDE.
We want them to be in the local repository. Simply point, it's too much
information for the developer to have to reconcile, especially since using an
archetype is likely the developer's first exposure to your project. It needs to
be simple.
What I'm looking for is a command that I can give the developer to import the
entries from a remote archetype catalog. A discovery mechanism so to speak.
I envision the following sequence to work:
{noformat}mvn archetype:import -DarchetypeCatalog=http://example.com/maven2
mvn archetype:generate{noformat}
At this point, the developer would see options for the imported archetypes. The
import goal could even download the archetype JAR files at the same time.
was:
If I've just published a new archetype, I need to be able to provide the
developer with a command that allows them to "educate" their local catalog
about the new archetypes that area available. Currently, it's possible to
specify an archetype catalog for a single run of the generate goal:
mvn archetype:generate -DarchetypeCatalog=http://example.com/maven2
But the catalog is transient. Those entries are not "remembered". The next time
I run the generate goal...
mvn archetype:generate
...the archetypes in the catalog provided in the previous command are not
offered as options.
This is especially problematic when using an IDE to create a new Maven project,
because the mechanism for providing an archetype catalog differs in each IDE.
We want them to be in the local repository. Simply point, it's too much
information for the developer to have to reconcile, especially since using an
archetype is likely the developer's first exposure to your project. It needs to
be simple.
What I'm looking for is a command that I can give the developer to import the
entries from a remote archetype catalog. A discovery mechanism so to speak.
I envision the following sequence to work:
mvn archetype:import -DarchetypeCatalog=http://example.com/maven2
mvn archetype:generate
At this point, the developer would see options for the imported archetypes. The
import goal could even download the archetype JAR files at the same time.
> add goal to import remote archetype catalog into local catalog
> --
>
> Key: ARCHETYPE-273
> URL: http://jira.codehaus.org/browse/ARCHETYPE-273
> Project: Maven Archetype
> Issue Type: New Feature
>Affects Versions: 2.0-alpha-4
>Reporter: Dan Allen
> Attachments:
> org.apache.maven.archetype.maven-archetype-ARCHETYPE-220_&_273_interactive_combo.patch,
> org.apache.maven.archetype.maven-archetype-ARCHETYPE-273_&_220_combo.patch
>
>
> If I've just published a new archetype, I need to be able to provide the
> developer with a command that allows them to "educate" their local catalog
> about the new archetypes that area available. Currently, it's possible to
> specify an archetype catalog for a single run of the generate goal:
> {noformat}mvn archetype:generate
> -DarchetypeCatalog=http://example.com/maven2{noformat}
> But the catalog is transient. Those entries are not "remembered". The next
> time I run the generate goal...
> {noformat}mvn archetype:generate{noformat}
> ...the archetypes in the catalog provided in the previous command are not
> offered as options.
> This is especially problematic when using an IDE to create a new Maven
> project, because the mechanism for providing an archetype catalog differs in
> each IDE. We want them to be in the local repository. Simply point, it's too
> much information for the developer to have to reconcile, especially since
> using an archetype is likely the developer's first exposure to your project.
> It needs to be simple.
> What I'm looking for is a command that I can give the developer to import the
> entries from a remote archetype catalog. A discovery mechanism so to speak.
> I envision the follow
[jira] Updated: (ARCHETYPE-167) Archiva : mvn archetype:create without guest user
[
http://jira.codehaus.org/browse/ARCHETYPE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated ARCHETYPE-167:
Description:
I try to launch mvn archetype:create with an archetype located on an archiva
proxy.
In archiva, when guest user isn't lock, it works, but when i lock guest user ,
it's not possible.
The command :
{noformat}mvn archetype:create
-DgroupId=com.myserver
-DartifactId=myserver
-DarchetypeGroupId=com.archetypes
-DarchetypeArtifactId=server_archetype
-DarchetypeVersion=2.0
-DremoteRepositories=http://url/{noformat}
I try to add -DRepositoryId but it's not ok.
it isn't possible to pass username and password to archiva.
was:
I try to launch mvn archetype:create with an archetype located on an archiva
proxy.
In archiva, when guest user isn't lock, it works, but when i lock guest user ,
it's not possible.
The command :
mvn archetype:create
-DgroupId=com.myserver
-DartifactId=myserver
-DarchetypeGroupId=com.archetypes
-DarchetypeArtifactId=server_archetype
-DarchetypeVersion=2.0
-DremoteRepositories=http://url/
I try to add -DRepositoryId but it's not ok.
it isn't possible to pass username and password to archiva.
> Archiva : mvn archetype:create without guest user
> -
>
> Key: ARCHETYPE-167
> URL: http://jira.codehaus.org/browse/ARCHETYPE-167
> Project: Maven Archetype
> Issue Type: Bug
> Components: Creator
> Environment: Windows XP / Maven 2.0.9 / Archiva 1.0.2
>Reporter: Florian
>
> I try to launch mvn archetype:create with an archetype located on an archiva
> proxy.
> In archiva, when guest user isn't lock, it works, but when i lock guest user
> , it's not possible.
> The command :
> {noformat}mvn archetype:create
> -DgroupId=com.myserver
> -DartifactId=myserver
> -DarchetypeGroupId=com.archetypes
> -DarchetypeArtifactId=server_archetype
> -DarchetypeVersion=2.0
> -DremoteRepositories=http://url/{noformat}
> I try to add -DRepositoryId but it's not ok.
> it isn't possible to pass username and password to archiva.
--
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: (ARCHETYPE-204) Add option to use remote repositories that are password protected
[
http://jira.codehaus.org/browse/ARCHETYPE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated ARCHETYPE-204:
Description:
When the archetype's are in a password protected repository you can't download
the archetype
Command used: {noformat}mvn archetype:generate
-DarchetypeGroupId=nl.func.quickstart -DarchetypeArtifactId=quickstart
-DarchetypeVersion=1.0 -DgroupId=nl.func.test -DartifactId=apple
-DarchetypeRepository=https://maven.func.nl{noformat}
There is a "archetypeRepository" option, but there is no option to bind a
server id from the settings.xml.
Could this, or some other solution, be added?
My current workaround is to use scpexe instead of https.
Command used:
{noformat}mvn archetype:generate -DarchetypeGroupId=nl.func.quickstart
-DarchetypeArtifactId=quickstart -DarchetypeVersion=1.0 -DgroupId=nl.func.test
-DartifactId=apple
-DarchetypeRepository=scpexe://maven.func.nl/var/sites/nl.func.maven/www/
-Darchetype.interactive=false{noformat}
was:
When the archetype's are in a password protected repository you can't download
the archetype
Command used: mvn archetype:generate -DarchetypeGroupId=nl.func.quickstart
-DarchetypeArtifactId=quickstart -DarchetypeVersion=1.0 -DgroupId=nl.func.test
-DartifactId=apple -DarchetypeRepository=https://maven.func.nl
There is a "archetypeRepository" option, but there is no option to bind a
server id from the settings.xml.
Could this, or some other solution, be added?
My current workaround is to use scpexe instead of https.
Command used:
mvn archetype:generate -DarchetypeGroupId=nl.func.quickstart
-DarchetypeArtifactId=quickstart -DarchetypeVersion=1.0 -DgroupId=nl.func.test
-DartifactId=apple
-DarchetypeRepository=scpexe://maven.func.nl/var/sites/nl.func.maven/www/
-Darchetype.interactive=false
> Add option to use remote repositories that are password protected
> -
>
> Key: ARCHETYPE-204
> URL: http://jira.codehaus.org/browse/ARCHETYPE-204
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Generator
>Affects Versions: 2.0-alpha-3
> Environment: mvn -version
> Maven version: 2.0.9
> Java version: 1.6.0_06
> OS name: "linux" version: "2.6.24-19-generic" arch: "i386" Family: "unix"
>Reporter: Martin Tilma
>Priority: Minor
> Fix For: 2.x
>
>
> When the archetype's are in a password protected repository you can't
> download the archetype
> Command used: {noformat}mvn archetype:generate
> -DarchetypeGroupId=nl.func.quickstart -DarchetypeArtifactId=quickstart
> -DarchetypeVersion=1.0 -DgroupId=nl.func.test -DartifactId=apple
> -DarchetypeRepository=https://maven.func.nl{noformat}
> There is a "archetypeRepository" option, but there is no option to bind a
> server id from the settings.xml.
> Could this, or some other solution, be added?
> My current workaround is to use scpexe instead of https.
> Command used:
> {noformat}mvn archetype:generate -DarchetypeGroupId=nl.func.quickstart
> -DarchetypeArtifactId=quickstart -DarchetypeVersion=1.0
> -DgroupId=nl.func.test -DartifactId=apple
> -DarchetypeRepository=scpexe://maven.func.nl/var/sites/nl.func.maven/www/
> -Darchetype.interactive=false{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] Closed: (ARCHETYPE-167) Archiva : mvn archetype:create without guest user
[
http://jira.codehaus.org/browse/ARCHETYPE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed ARCHETYPE-167.
---
Resolution: Duplicate
same issue as ARCHETYPE-204
ARCHETYPE-206 added documentation for a workaround
> Archiva : mvn archetype:create without guest user
> -
>
> Key: ARCHETYPE-167
> URL: http://jira.codehaus.org/browse/ARCHETYPE-167
> Project: Maven Archetype
> Issue Type: Bug
> Components: Creator
> Environment: Windows XP / Maven 2.0.9 / Archiva 1.0.2
>Reporter: Florian
>
> I try to launch mvn archetype:create with an archetype located on an archiva
> proxy.
> In archiva, when guest user isn't lock, it works, but when i lock guest user
> , it's not possible.
> The command :
> {noformat}mvn archetype:create
> -DgroupId=com.myserver
> -DartifactId=myserver
> -DarchetypeGroupId=com.archetypes
> -DarchetypeArtifactId=server_archetype
> -DarchetypeVersion=2.0
> -DremoteRepositories=http://url/{noformat}
> I try to add -DRepositoryId but it's not ok.
> it isn't possible to pass username and password to archiva.
--
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: (MDOAP-28) Remove developers/contributors having role 'emeritus'
[ http://jira.codehaus.org/browse/MDOAP-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Knecht updated MDOAP-28: -- Attachment: emeritus_test.patch > Remove developers/contributors having role 'emeritus' > -- > > Key: MDOAP-28 > URL: http://jira.codehaus.org/browse/MDOAP-28 > Project: Maven 2.x DOAP Plugin > Issue Type: Improvement >Affects Versions: 1.1 > Environment: All >Reporter: Felix Knecht > Attachments: emeritus.patch, emeritus_test.patch > > > In various Apache projects it's common to leave developers who are no longer > active in the project still the developers section of the pom.xml but set the > role to 'Emeritus'. Such developers shouldn't be listed in the DOAP file as > maintainer. > Patch doesn't adds this developers (and contributors) as maintainer. -- 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: (MCLEAN-46) Enable useDefaultExcludes per Fileset
[ http://jira.codehaus.org/browse/MCLEAN-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MCLEAN-46. --- Resolution: Fixed Fix Version/s: 2.5 Assignee: Benjamin Bentmann Applied in [r1026633|http://svn.apache.org/viewvc?view=revision&revision=1026633], thanks! > Enable useDefaultExcludes per Fileset > - > > Key: MCLEAN-46 > URL: http://jira.codehaus.org/browse/MCLEAN-46 > Project: Maven 2.x Clean Plugin > Issue Type: Improvement >Affects Versions: 2.4.1 >Reporter: Maik Richey >Assignee: Benjamin Bentmann > Fix For: 2.5 > > Attachments: useDefaultExcludes.patch > > > Needed to clean some source folders from generated classes. So I added a > profile for doing that and found that my .svn directories are gone as well. > By looking at the code I discovered that usage of was > almost implemented. So, I did the rest (see patch attached). -- 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: (MCOMPILER-139) test-compile doesn't honor @SuppressWarnings("deprecation") as compile does
[
http://jira.codehaus.org/browse/MCOMPILER-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MCOMPILER-139.
---
Resolution: Not A Bug
Assignee: Benjamin Bentmann
Please report this against Oracle's {{javac}}, the Compiler Plugin merely
forwards the warning message received from the compiler bundled with the JDK.
> test-compile doesn't honor @SuppressWarnings("deprecation") as compile does
> ---
>
> Key: MCOMPILER-139
> URL: http://jira.codehaus.org/browse/MCOMPILER-139
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 2.1, 2.3.2
>Reporter: Dominique Jean-Prost
>Assignee: Benjamin Bentmann
> Attachments: execution.log, test.zip
>
>
> /test/src/main/java/test/DeprecatedObject.java :
> [co...@deprecated
> public class DeprecatedObject {
> public DeprecatedObject() {
> }
> }[/code]
> /test/src/main/java/test/DeprecatedMain.java :
> [co...@suppresswarnings("deprecation")
> public class DeprecatedMain {
> @SuppressWarnings("unused")
> private final Date d = new Date("20/10/2006");
> public DeprecatedObject test() {
> return null;
> }
> }[/code]
> /test/src/test/java/test/DeprecatedTest.java :
> [co...@suppresswarnings("deprecation")
> public class DeprecatedTest {
> @SuppressWarnings("unused")
> private final Date d = new Date("2010/2010");
> public void test(final DeprecatedObject obj) {
> }
> }[/code]
> mvn clean test-compile :
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ test ---
> [INFO] Deleting C:\workspace\test\target
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ test
> ---
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ test ---
> [WARNING] File encoding has not been set, using platform encoding Cp1252,
> i.e. build is platform dependent!
> [INFO] Compiling 2 source files to C:\workspace\test\target\classes
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources)
> @ test ---
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @
> test ---
> [WARNING] File encoding has not been set, using platform encoding Cp1252,
> i.e. build is platform dependent!
> [INFO] Compiling 1 source file to C:\workspace\test\target\test-classes
> [WARNING] \workspace\test\src\test\java\test\DeprecatedTest.java:[13,27]
> [deprecation] test.DeprecatedObject in test has been deprecated
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> --> Although both DeprecatedMain and DeprecatedTest use DeprecatedObject and
> both have @SuppressWarnings("deprecation") at class level, the compile output
> shows a warning. The warning occurs only in test-compile.
> Please note that if both stops using DeprecatedObject (remove te two "test"
> method from objects), then copiler output doesn't mention deprecated.
--
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: (MCOMPILER-136) The description of the skip parameter of the testCompile mojo is incorrect
[ http://jira.codehaus.org/browse/MCOMPILER-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MCOMPILER-136. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Benjamin Bentmann Fixed in [r1026646|http://svn.apache.org/viewvc?view=revision&revision=1026646]. > The description of the skip parameter of the testCompile mojo is incorrect > -- > > Key: MCOMPILER-136 > URL: http://jira.codehaus.org/browse/MCOMPILER-136 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: n/a >Reporter: Anders Hammar >Assignee: Benjamin Bentmann >Priority: Trivial > Fix For: 2.4 > > > The description of the skip parameter of TestCompilerMojo should read: > "Set this to 'true' to bypass compilation of test sources." > I also think that the text "Its use is NOT RECOMMENDED, but quite convenient > on occasion." should be removed. -- 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: (MJAVADOC-284) detectOfflineLinks sets off extra spurious executions of javadoc
[ http://jira.codehaus.org/browse/MJAVADOC-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240771#action_240771 ] Herve Boutemy commented on MJAVADOC-284: can you provide a sample project causing such problem, please? > detectOfflineLinks sets off extra spurious executions of javadoc > > > Key: MJAVADOC-284 > URL: http://jira.codehaus.org/browse/MJAVADOC-284 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.6.1 >Reporter: Benson Margulies > > I have an aggregate project. In pluginManagement, I spec out javadoc:jar. In > the leaf projects, I turn it on with an ordinary for the plugin. > If I leave detectOfflineLinks with its default value of true, the javadoc > plugin uses the invoker plugin to relaunch itself, recursively, complaining > that it hasn't been run on one or another of the projects. Note that, when > this happens, it is 'swimming upstream' -- it is processing project A, it > invokes itself on project B, where B depends on A, not the other way around. > If I run maven just in the leaf directories all is well. The trouble only > happens when running maven from the aggregating parent. > Just to clarify, in case I don't get a test case together too soon ... > external/corporate parent: > javadoc only mentioned in the section. > aggregating parent: > javadoc only mentioned in pluginManagement, setting up execution of > javadoc:jar. > leaf: > A very plain 'plugin' element just to turn on the configuration from plugin > management. > mvn run from leaf: all is well. > mvn run from aggregating parent: lots of extra 'invoker' invocations of > javadoc on projects that have dependencies on the current project. -- 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: (MJAVADOC-297) NullPointerException in AbstractFixJavadocMojo.writeParamTag()
[
http://jira.codehaus.org/browse/MJAVADOC-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MJAVADOC-297:
---
Description:
While attempting to run the javadoc:fix goal against source code, v2.7 of the
javadoc plugin crashed as follows:
{noformat}[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.writeParamTag(AbstractFixJavadocMojo.java:1958)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateJavadocTags(AbstractFixJavadocMojo.java:1842)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateJavadocTags(AbstractFixJavadocMojo.java:1747)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateJavadocComment(AbstractFixJavadocMojo.java:1658)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateEntityComment(AbstractFixJavadocMojo.java:1527)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.fixMethodComment(AbstractFixJavadocMojo.java:1391)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.processFix(AbstractFixJavadocMojo.java:993)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.execute(AbstractFixJavadocMojo.java:405)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
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)
{noformat}
was:
While attempting to run the javadoc:fix goal against source code, v2.7 of the
javadoc plugin crashed as follows:
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.writeParamTag(AbstractFixJavadocMojo.java:1958)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateJavadocTags(AbstractFixJavadocMojo.java:1842)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateJavadocTags(AbstractFixJavadocMojo.java:1747)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateJavadocComment(AbstractFixJavadocMojo.java:1658)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateEntityComment(AbstractFixJavadocMojo.java:1527)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.fixMethodComment(AbstractFixJavadocMojo.java:1391)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.processFix(AbstractFixJavadocMojo.java:993)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.execute(AbstractFixJavadocMojo.java:405)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycle
