[jira] (MNG-5586) Deploy effective pom
nicolas de loof created MNG-5586: Summary: Deploy effective pom Key: MNG-5586 URL: https://jira.codehaus.org/browse/MNG-5586 Project: Maven 2 & 3 Issue Type: Improvement Components: Deployment Reporter: nicolas de loof When deploying pom for an artifact, maven deploys the actual file used to build. As this one can define profiles, and build can rely on command line properties that change actual project model, the deployed pom.xml may not reflect the one used by maven to build the project. Also, this prevent changes to happen in pom.xml format (wildcard exclusion for sample) without breaking compatibility. Maven should deploy effective pom when artifact doesn't define pom packaging -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5585) match server credentials based on server realm
nicolas de loof created MNG-5585: Summary: match server credentials based on server realm Key: MNG-5585 URL: https://jira.codehaus.org/browse/MNG-5585 Project: Maven 2 & 3 Issue Type: Improvement Components: Settings Affects Versions: 3.x / Backlog Reporter: nicolas de loof credentials for repositories are identified based on arbitrary ID. This is error prone and fragile design, especially as there's no way to diagnose which credentials are used (see MNG-5584). A realm-based server matching would better follow the way HTTP security is defined, and could be easily used for other protocols based (for sample) on domain name. xxx [optional protocol://]repo.acme.com .. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5584) log credentials source when failing to access a repository
nicolas de loof created MNG-5584: Summary: log credentials source when failing to access a repository Key: MNG-5584 URL: https://jira.codehaus.org/browse/MNG-5584 Project: Maven 2 & 3 Issue Type: Improvement Components: Dependencies, Deployment Reporter: nicolas de loof When some repository authentication fail, maven just logs the status : Could not transfer artifact from/to (): Not authorized, ReasonPhrase:Unauthorized. but don't let user know if credentials are well set and which one it used. I'd like it logs credentials source it used trying to access repository, like "using server credentials from ", source being some settings.xml path or equivalent. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-346) LightWeight http wagon not thread-safe
[ https://jira.codehaus.org/browse/WAGON-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292730#comment-292730 ] nicolas de loof commented on WAGON-346: --- @Mark you're right, so the only way to get this fixed is to deprecate wagon-http-lightweight and definitively remove it from wagon project as URLConnection can't be used in a concurrent context > LightWeight http wagon not thread-safe > -- > > Key: WAGON-346 > URL: https://jira.codehaus.org/browse/WAGON-346 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-http-lightweight >Affects Versions: 1.0 > Environment: maven 3 with Aether >Reporter: nicolas de loof > Fix For: 1.1, 2.0 > > > Aether (maven3) by default parallelized metadata resolution on 4 threads > (aether.metadataResolver.threads) and artifacts downloading on 5 > (maven.artifact.threads). > In such context, Wagon is not used sequentially. > LightWeightHttpWagon is designed for mono-thread, sequential usage. It rely > on system properties and on setting/resetting java.net.Authenticator > singleton. > The result is that, in some cases (typically : when settings defines many > repositories with various credentials), credentials may not apply and > download will fail > A potential fix is > - to use Java5 URL.openConnection(Proxy) instead of using system properties > - to use a shared, singleton java.net.Authenticator that lookup repositories > to match the requested URL -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (WAGON-346) LightWeight http wagon not thread-safe
[ https://jira.codehaus.org/browse/WAGON-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed WAGON-346. - Resolution: Fixed Fix Version/s: 2.0 1.x Fixed in 1.x using a class level synchronized block > LightWeight http wagon not thread-safe > -- > > Key: WAGON-346 > URL: https://jira.codehaus.org/browse/WAGON-346 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-http-lightweight >Affects Versions: 1.0 > Environment: maven 3 with Aether >Reporter: nicolas de loof > Fix For: 1.x, 2.0 > > > Aether (maven3) by default parallelized metadata resolution on 4 threads > (aether.metadataResolver.threads) and artifacts downloading on 5 > (maven.artifact.threads). > In such context, Wagon is not used sequentially. > LightWeightHttpWagon is designed for mono-thread, sequential usage. It rely > on system properties and on setting/resetting java.net.Authenticator > singleton. > The result is that, in some cases (typically : when settings defines many > repositories with various credentials), credentials may not apply and > download will fail > A potential fix is > - to use Java5 URL.openConnection(Proxy) instead of using system properties > - to use a shared, singleton java.net.Authenticator that lookup repositories > to match the requested URL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WAGON-346) LightWeight http wagon not thread-safe
[ https://jira.codehaus.org/browse/WAGON-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277264#comment-277264 ] nicolas de loof commented on WAGON-346: --- Fixed on 2.x branch, I'll now try to find a workaround on 1.x branch > LightWeight http wagon not thread-safe > -- > > Key: WAGON-346 > URL: https://jira.codehaus.org/browse/WAGON-346 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-http-lightweight >Affects Versions: 1.0 > Environment: maven 3 with Aether >Reporter: nicolas de loof > > Aether (maven3) by default parallelized metadata resolution on 4 threads > (aether.metadataResolver.threads) and artifacts downloading on 5 > (maven.artifact.threads). > In such context, Wagon is not used sequentially. > LightWeightHttpWagon is designed for mono-thread, sequential usage. It rely > on system properties and on setting/resetting java.net.Authenticator > singleton. > The result is that, in some cases (typically : when settings defines many > repositories with various credentials), credentials may not apply and > download will fail > A potential fix is > - to use Java5 URL.openConnection(Proxy) instead of using system properties > - to use a shared, singleton java.net.Authenticator that lookup repositories > to match the requested URL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (WAGON-347) Support preemtive authentication
[ https://jira.codehaus.org/browse/WAGON-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed WAGON-347. - Resolution: Fixed Fix Version/s: 2.0 Assignee: nicolas de loof fixed in both 1.x and 2.x branches > Support preemtive authentication > > > Key: WAGON-347 > URL: https://jira.codehaus.org/browse/WAGON-347 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http-lightweight >Reporter: nicolas de loof >Assignee: nicolas de loof >Priority: Minor > Fix For: 2.0 > > > Set Authorization header on HttpUrlConnection to get preemptive > authentication and avoid unnecessary network traffic -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (WAGON-347) Support preemtive authentication
Support preemtive authentication Key: WAGON-347 URL: https://jira.codehaus.org/browse/WAGON-347 Project: Maven Wagon Issue Type: Improvement Components: wagon-http-lightweight Reporter: nicolas de loof Priority: Minor Set Authorization header on HttpUrlConnection to get preemptive authentication and avoid unnecessary network traffic -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (WAGON-346) LightWeight http wagon not thread-safe
LightWeight http wagon not thread-safe -- Key: WAGON-346 URL: https://jira.codehaus.org/browse/WAGON-346 Project: Maven Wagon Issue Type: Bug Components: wagon-http-lightweight Affects Versions: 1.0 Environment: maven 3 with Aether Reporter: nicolas de loof Aether (maven3) by default parallelized metadata resolution on 4 threads (aether.metadataResolver.threads) and artifacts downloading on 5 (maven.artifact.threads). In such context, Wagon is not used sequentially. LightWeightHttpWagon is designed for mono-thread, sequential usage. It rely on system properties and on setting/resetting java.net.Authenticator singleton. The result is that, in some cases (typically : when settings defines many repositories with various credentials), credentials may not apply and download will fail A potential fix is - to use Java5 URL.openConnection(Proxy) instead of using system properties - to use a shared, singleton java.net.Authenticator that lookup repositories to match the requested URL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MENFORCER-19) Add an option to enforce dependencyManagement
[
http://jira.codehaus.org/browse/MENFORCER-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MENFORCER-19.
Resolution: Won't Fix
With some flags set,
[maven-dependency-plugin|http://maven.apache.org/plugins/maven-dependency-plugin/analyze-dep-mgt-mojo.html]
can be used to enforce dependencyManagement. A little verbose, but does the
job well.
{code:xml}
maven-dependency-plugin
analyze-dep-mgt
verify
true
false
{code}
> Add an option to enforce dependencyManagement
> -
>
> Key: MENFORCER-19
> URL: http://jira.codehaus.org/browse/MENFORCER-19
> Project: Maven 2.x Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
>Reporter: Carlos Sanchez
>
> Add something to the dependencyManagement section like
> true
> to make build fail if a subproject uses a different version
> Currently a subproject can specify the version of a dependency already
> defined in dependencyManagement, which is error prone
--
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: (MDEP-269) Goal to convert a legacy /lib/*.jar to maven dependencies list
[ http://jira.codehaus.org/browse/MDEP-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof updated MDEP-269: - Attachment: MDEP-269.patch > Goal to convert a legacy /lib/*.jar to maven dependencies list > -- > > Key: MDEP-269 > URL: http://jira.codehaus.org/browse/MDEP-269 > Project: Maven 2.x Dependency Plugin > Issue Type: New Feature >Reporter: nicolas de loof >Assignee: Brian Fox >Priority: Minor > Attachments: MDEP-269.patch > > > To convert a legacy ant/script-based project to Maven first step is to > identify all dependencies as maven artifacts. This can be long and subject to > errors. > Using Nexus index [1], Nexus REST API [2], or any other tooling, the plugin > could automagically search the available repositories for known artifacts to > match the content of a /lib directory, and output a POM formatted list of > dependencies, also warning for unresolved ones. > alf-maven-osecm plugin allready provides such feature using a custom CSV > format, this code can be used as a dev sample. > [1] http://www.sonatype.com/people/2009/06/nexus-indexer-api-part-2/ > [2] https://docs.sonatype.com/display/NX/Nexus+Rest+API > [3] > http://alf-maven-osecm.googlecode.com/svn/trunk/dependenciesGenerator-maven-plugin/dependenciesGenerator-maven-plugin/ > http://opensourceecm.fr/maven/dependenciesGenerator/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] Updated: (MDEP-269) Goal to convert a legacy /lib/*.jar to maven dependencies list
[ http://jira.codehaus.org/browse/MDEP-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof updated MDEP-269: - Description: To convert a legacy ant/script-based project to Maven first step is to identify all dependencies as maven artifacts. This can be long and subject to errors. Using Nexus index [1], Nexus REST API [2], or any other tooling, the plugin could automagically search the available repositories for known artifacts to match the content of a /lib directory, and output a POM formatted list of dependencies, also warning for unresolved ones. alf-maven-osecm plugin allready provides such feature using a custom CSV format, this code can be used as a dev sample. [1] http://www.sonatype.com/people/2009/06/nexus-indexer-api-part-2/ [2] https://docs.sonatype.com/display/NX/Nexus+Rest+API [3] http://alf-maven-osecm.googlecode.com/svn/trunk/dependenciesGenerator-maven-plugin/dependenciesGenerator-maven-plugin/ http://opensourceecm.fr/maven/dependenciesGenerator/index.html was: To convert a legacy ant/script-based project to Maven first step is to identify all dependencies as maven artifacts. This can be long and subject to errors. Using Nexus index [1], Nexus REST API [2], or any other tooling, the plugin could automagically search the available repositories for known artifacts to match the content of a /lib directory, and output a POM formatted list of dependencies, also warning for unresolved ones. alf-maven-osecm plugin allready provides such feature using a custom CSV format, this code can be used as a dev sample. [1] http://www.sonatype.com/people/2009/06/nexus-indexer-api-part-2/ [2] https://docs.sonatype.com/display/NX/Nexus+Rest+API [3] http://alf-maven-osecm.googlecode.com/svn/trunk/dependenciesGenerator-maven-plugin/dependenciesGenerator-maven-plugin/ > Goal to convert a legacy /lib/*.jar to maven dependencies list > -- > > Key: MDEP-269 > URL: http://jira.codehaus.org/browse/MDEP-269 > Project: Maven 2.x Dependency Plugin > Issue Type: New Feature >Reporter: nicolas de loof >Assignee: Brian Fox >Priority: Minor > > To convert a legacy ant/script-based project to Maven first step is to > identify all dependencies as maven artifacts. This can be long and subject to > errors. > Using Nexus index [1], Nexus REST API [2], or any other tooling, the plugin > could automagically search the available repositories for known artifacts to > match the content of a /lib directory, and output a POM formatted list of > dependencies, also warning for unresolved ones. > alf-maven-osecm plugin allready provides such feature using a custom CSV > format, this code can be used as a dev sample. > [1] http://www.sonatype.com/people/2009/06/nexus-indexer-api-part-2/ > [2] https://docs.sonatype.com/display/NX/Nexus+Rest+API > [3] > http://alf-maven-osecm.googlecode.com/svn/trunk/dependenciesGenerator-maven-plugin/dependenciesGenerator-maven-plugin/ > http://opensourceecm.fr/maven/dependenciesGenerator/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: (MDEP-269) Goal to convert a legacy /lib/*.jar to maven dependencies list
Goal to convert a legacy /lib/*.jar to maven dependencies list -- Key: MDEP-269 URL: http://jira.codehaus.org/browse/MDEP-269 Project: Maven 2.x Dependency Plugin Issue Type: New Feature Reporter: nicolas de loof Assignee: Brian Fox Priority: Minor To convert a legacy ant/script-based project to Maven first step is to identify all dependencies as maven artifacts. This can be long and subject to errors. Using Nexus index [1], Nexus REST API [2], or any other tooling, the plugin could automagically search the available repositories for known artifacts to match the content of a /lib directory, and output a POM formatted list of dependencies, also warning for unresolved ones. alf-maven-osecm plugin allready provides such feature using a custom CSV format, this code can be used as a dev sample. [1] http://www.sonatype.com/people/2009/06/nexus-indexer-api-part-2/ [2] https://docs.sonatype.com/display/NX/Nexus+Rest+API [3] http://alf-maven-osecm.googlecode.com/svn/trunk/dependenciesGenerator-maven-plugin/dependenciesGenerator-maven-plugin/ -- 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-546) regression introduced in MRELEASE-261
[
http://jira.codehaus.org/browse/MRELEASE-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MRELEASE-546.
Resolution: Fixed
Fix Version/s: 2.1
Committed at rev 933531.
> regression introduced in MRELEASE-261
> -
>
> Key: MRELEASE-546
> URL: http://jira.codehaus.org/browse/MRELEASE-546
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.0
>Reporter: nicolas de loof
>Assignee: nicolas de loof
> Fix For: 2.1
>
>
> Using hierachical projet structure, when the parent project is not first one
> in the reactor, getCommonBasedir fails to detect the common basedir
> {code}
> public void
> testGetCommonBasedirOfRegularMultiModuleRootNotBeeingFirstInReactor()
> throws Exception
> {
> assertEquals( "/working/directory/flat-multi-module",
> ReleaseUtil.getCommonBasedir( Arrays.asList(
> new MavenProject[]{
> createProject( "/working/directory/flat-multi-module/core" ),
> createProject( "/working/directory/flat-multi-module" ),
> createProject( "/working/directory/flat-multi-module/webapp"
> )} ), '/' ) );
> }
> {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] Work started: (MRELEASE-546) regression introduced in MRELEASE-261
[
http://jira.codehaus.org/browse/MRELEASE-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MRELEASE-546 started by nicolas de loof.
> regression introduced in MRELEASE-261
> -
>
> Key: MRELEASE-546
> URL: http://jira.codehaus.org/browse/MRELEASE-546
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.0
>Reporter: nicolas de loof
>Assignee: nicolas de loof
>
> Using hierachical projet structure, when the parent project is not first one
> in the reactor, getCommonBasedir fails to detect the common basedir
> {code}
> public void
> testGetCommonBasedirOfRegularMultiModuleRootNotBeeingFirstInReactor()
> throws Exception
> {
> assertEquals( "/working/directory/flat-multi-module",
> ReleaseUtil.getCommonBasedir( Arrays.asList(
> new MavenProject[]{
> createProject( "/working/directory/flat-multi-module/core" ),
> createProject( "/working/directory/flat-multi-module" ),
> createProject( "/working/directory/flat-multi-module/webapp"
> )} ), '/' ) );
> }
> {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: (MRELEASE-546) regression introduced in MRELEASE-261
regression introduced in MRELEASE-261
-
Key: MRELEASE-546
URL: http://jira.codehaus.org/browse/MRELEASE-546
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: perform
Affects Versions: 2.0
Reporter: nicolas de loof
Using hierachical projet structure, when the parent project is not first one in
the reactor, getCommonBasedir fails to detect the common basedir
{code}
public void
testGetCommonBasedirOfRegularMultiModuleRootNotBeeingFirstInReactor()
throws Exception
{
assertEquals( "/working/directory/flat-multi-module",
ReleaseUtil.getCommonBasedir( Arrays.asList(
new MavenProject[]{
createProject( "/working/directory/flat-multi-module/core" ),
createProject( "/working/directory/flat-multi-module" ),
createProject( "/working/directory/flat-multi-module/webapp" )}
), '/' ) );
}
{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] Closed: (MECLIPSE-568) Some compile dependencies are not added to .classpath since 2.6
[
http://jira.codehaus.org/browse/MECLIPSE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MECLIPSE-568.
Resolution: Fixed
fixed by MECLIPSE-594
> Some compile dependencies are not added to .classpath since 2.6
> ---
>
> Key: MECLIPSE-568
> URL: http://jira.codehaus.org/browse/MECLIPSE-568
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: AJDT support
>Affects Versions: 2.6
>Reporter: Rustam Abdullaev
>Priority: Critical
> Fix For: 2.8
>
>
> No matter what I try, the following dependency is never added to the
> .classpath since version 2.6, even if it is specified explicitly:
> {code:xml}
>
> org.aspectj
> aspectjweaver
> 1.6.1
>
> {code}
> The same happens to aspectjrt
--
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: (MECLIPSE-584) No eclipse classpath entries generated for aspectj dependencies
[ http://jira.codehaus.org/browse/MECLIPSE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MECLIPSE-584. Resolution: Fixed fixed by MECLIPSE-594 > No eclipse classpath entries generated for aspectj dependencies > --- > > Key: MECLIPSE-584 > URL: http://jira.codehaus.org/browse/MECLIPSE-584 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: AJDT support > Environment: Fedora 11 > Sun Java >Reporter: Ole Ersoy >Priority: Minor > Fix For: 2.8 > > > When I run eclipse:eclipse .classpath entries for the following elements > don't get added: > > org.aspectj > aspectjrt > 1.5.4 > > > > org.aspectj > aspectjweaver > 1.5.4 > > The dependencies are in the repository and I can add them manually myself > like this: >path="M2_REPO/org/aspectj/aspectjrt/1.5.4/aspectjrt-1.5.4.jar"/> >path="M2_REPO/org/aspectj/aspectjweaver/1.5.4/aspectjweaver-1.5.4.jar"/> > I really thought this had to be a user error, so I tried taking some > dependency declarations that work, and just changing the body values to > correspond with the bodies of the aspectj dependency declarations. It still > does not work. -- 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: (MECLIPSE-569) eclipse:eclipse does not add all libraries to .classpath
[ http://jira.codehaus.org/browse/MECLIPSE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MECLIPSE-569. Resolution: Fixed fixed by MECLIPSE-594 > eclipse:eclipse does not add all libraries to .classpath > > > Key: MECLIPSE-569 > URL: http://jira.codehaus.org/browse/MECLIPSE-569 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: AJDT support >Affects Versions: 2.6 > Environment: Ubuntu 9.04, sun java 1.6, maven 2.1.0 and maven 2.0.9 >Reporter: Armands Graube > Fix For: 2.8 > > Attachments: pom.xml > > > Maven eclipse plugin 2.6 does not add aspectj:aspectjtools:1.5.3 library > entries to .classpath file, could not reproduce with other libraries. When > changed back to eclipse plugin 2.5, .classpath contains alll the correct > entries. Not sure, maybe this has to do something with the specific library? > Attached sample pom.xml where you get the library added to .classpath if > uncommented version 2.5 and not add if uncommented version 2.6 -- 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: (MECLIPSE-594) set AJDT version parameter to none by default
[ http://jira.codehaus.org/browse/MECLIPSE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MECLIPSE-594. Resolution: Fixed Assignee: nicolas de loof (was: Arnaud Heritier) disabling AJDT support by default > set AJDT version parameter to none by default > - > > Key: MECLIPSE-594 > URL: http://jira.codehaus.org/browse/MECLIPSE-594 > Project: Maven 2.x Eclipse Plugin > Issue Type: Task > Components: AJDT support >Affects Versions: 2.6, 2.7 >Reporter: Arnaud Heritier >Assignee: nicolas de loof > Fix For: 2.8 > > > It will be easier for our user if by default AJDT support is off. -- 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: (MECLIPSE-156) Plugin should support setting file encoding
[ http://jira.codehaus.org/browse/MECLIPSE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MECLIPSE-156. Resolution: Fixed Fix Version/s: 2.8 Assignee: nicolas de loof plugin now uses mvan-compiler-plugin # encoding to generate the adequate .settings > Plugin should support setting file encoding > --- > > Key: MECLIPSE-156 > URL: http://jira.codehaus.org/browse/MECLIPSE-156 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Reporter: Ralph Poellath >Assignee: nicolas de loof > Fix For: 2.8 > > Attachments: maven-eclipse-plugin-2.5.1.tar.gz, > MECLIPSE-156-maven-eclipse-plugin.patch > > > The plugin should support setting Eclipse's text file encoding on a > per-project basis. -- 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: (MECLIPSE-558) Ignoring listed AspectJ dependencies
[ http://jira.codehaus.org/browse/MECLIPSE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MECLIPSE-558. Resolution: Fixed Assignee: nicolas de loof Completed: At revision: 825429 > Ignoring listed AspectJ dependencies > > > Key: MECLIPSE-558 > URL: http://jira.codehaus.org/browse/MECLIPSE-558 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: AJDT support >Affects Versions: 2.6, 2.7 >Reporter: Dale Peakall >Assignee: nicolas de loof > Fix For: 2.8 > > > When AJDT support is enabled, the plugin ignores any dependencies that > include the term "aspectj" in the artifactId: these include aspectjrt.jar, > aspectjweaver.jar and aspectjtools.jar. Instead the project gets created > with a link to the AspectJ Runtime Library "Folder" which just contains > aspectjrt.jar. However, if the project depends on the other AspectJ > artifacts, e.g. aspectjweaver.jar (because it uses load-time-weaving) it is > broken and no amount of POM tweaking will get it back in there. > Using the none is fine if the project doesn't > include any aspects - but if it does it needs AJDT to compile the aspect - > but also needs the other AspectJ artifacts (that were specified in the POM) > to run Unit Tests etc. > At a minimum the plugin should be modified to only replace aspectjrt. > However, I am generally uncomfortable with the whole replacement concept. As > long as projects specify the appropriate dependencies then AJDT will be able > to compile and run the project (i.e. the special "AspectJ Runtime Library" > folder is not required). This will also ensure that a consistent version of > AspectJ is used (the version provided by Eclipse need not be the same as > specified in the POM). -- 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-383) svn inconsistent line ending style
[
http://jira.codehaus.org/browse/MRELEASE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194750#action_194750
]
nicolas de loof commented on MRELEASE-383:
--
svn:eol-style has been set to ensure reproductibility.
Can you please check the "expected" pom layout ?
test pass on CI server :-/
> svn inconsistent line ending style
> --
>
> Key: MRELEASE-383
> URL: http://jira.codehaus.org/browse/MRELEASE-383
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Barrie Treloar
>Assignee: nicolas de loof
> Fix For: 2.0-beta-10
>
>
> The problem occurs in the CDATA section of the maven-eclipse-plugin -
> when setting the contents of the .checkstyle file.
> {code:xml}
> pom.xml
> ...
>
> org.apache.maven.plugins
> maven-eclipse-plugin
>
>true
>
>
> com.atlassw.tools.eclipse.checkstyle.CheckstyleBuilder
>
>
>
> com.atlassw.tools.eclipse.checkstyle.CheckstyleNature
>
>
>
>.checkstyle
>
>
>
>
>
>
>
>
> {code}
> When this file is transformed the CDATA section has LF only.
> On windows it should have CR LF.
> I suspect because it uses \n instead of System.getProperty( line.separator );
--
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-383) svn inconsistent line ending style
[
http://jira.codehaus.org/browse/MRELEASE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MRELEASE-383.
Assignee: nicolas de loof
Resolution: Fixed
Fix Version/s: 2.0-beta-10
CDATA sections are now filtered to ensure consistent line ending in transformed
POM
> svn inconsistent line ending style
> --
>
> Key: MRELEASE-383
> URL: http://jira.codehaus.org/browse/MRELEASE-383
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Barrie Treloar
>Assignee: nicolas de loof
> Fix For: 2.0-beta-10
>
>
> The problem occurs in the CDATA section of the maven-eclipse-plugin -
> when setting the contents of the .checkstyle file.
> {code:xml}
> pom.xml
> ...
>
> org.apache.maven.plugins
> maven-eclipse-plugin
>
>true
>
>
> com.atlassw.tools.eclipse.checkstyle.CheckstyleBuilder
>
>
>
> com.atlassw.tools.eclipse.checkstyle.CheckstyleNature
>
>
>
>.checkstyle
>
>
>
>
>
>
>
>
> {code}
> When this file is transformed the CDATA section has LF only.
> On windows it should have CR LF.
> I suspect because it uses \n instead of System.getProperty( line.separator );
--
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: (MECLIPSE-580) sourceExcludes is applied to src/test/java, not to src/main/java
sourceExcludes is applied to src/test/java, not to src/main/java Key: MECLIPSE-580 URL: http://jira.codehaus.org/browse/MECLIPSE-580 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.7 Reporter: nicolas de loof With maven-eclipse-plugin 2.7 **/emul/**/*.java runing mvn eclipse:m2eclipse the generated .classpath file is ... The excluding attribute is set but not on the expected element -- 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: (MCHECKSTYLE-105) Update to Checkstyle 5.0
[ http://jira.codehaus.org/browse/MCHECKSTYLE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179170#action_179170 ] nicolas de loof commented on MCHECKSTYLE-105: - You don't need to convince me about java5 I plan to call for a vote on checkstyle plugin for a 2.3. I could also start the 2.4 branch now and deploy a first SNAPSHOT The only reason this is not yet done is lack of time ! > Update to Checkstyle 5.0 > > > Key: MCHECKSTYLE-105 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-105 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Felix Röthenbacher >Assignee: nicolas de loof > Fix For: 2.4 > > Attachments: patch.diff, update-to-5.0beta2.patch > > > Checkstyle 5.0-beta01 adds support for generics, etc. > See > http://checkstyle.sourceforge.net/5.x/releasenotes.html > for a list of new features. > Note: Prerequisite is that checkstyle-all jar, version 5.0-beta01 is > available from a public Maven repository. > Patch updates plugin to changed API / implementation. -- 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: (MCHECKSTYLE-105) Update to Checkstyle 5.0
[ http://jira.codehaus.org/browse/MCHECKSTYLE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179137#action_179137 ] nicolas de loof commented on MCHECKSTYLE-105: - 2.3-20090518.081942-2 was my mistake : we decided the plugin should have a last release with java 1.4 support before moving to java5 (and checkstyle 5). For this reason this issue has been reverted and delayed to a future 2.4 - there is no snapshot yet (you can build and install one in your own managed repository if you wish) > Update to Checkstyle 5.0 > > > Key: MCHECKSTYLE-105 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-105 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Felix Röthenbacher >Assignee: nicolas de loof > Fix For: 2.4 > > Attachments: patch.diff, update-to-5.0beta2.patch > > > Checkstyle 5.0-beta01 adds support for generics, etc. > See > http://checkstyle.sourceforge.net/5.x/releasenotes.html > for a list of new features. > Note: Prerequisite is that checkstyle-all jar, version 5.0-beta01 is > available from a public Maven repository. > Patch updates plugin to changed API / implementation. -- 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: (MCHECKSTYLE-105) Update to Checkstyle 5.0
[ http://jira.codehaus.org/browse/MCHECKSTYLE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof updated MCHECKSTYLE-105: Fix Version/s: (was: 2.3) 2.4 > Update to Checkstyle 5.0 > > > Key: MCHECKSTYLE-105 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-105 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Felix Röthenbacher >Assignee: nicolas de loof > Fix For: 2.4 > > Attachments: patch.diff, update-to-5.0beta2.patch > > > Checkstyle 5.0-beta01 adds support for generics, etc. > See > http://checkstyle.sourceforge.net/5.x/releasenotes.html > for a list of new features. > Note: Prerequisite is that checkstyle-all jar, version 5.0-beta01 is > available from a public Maven repository. > Patch updates plugin to changed API / implementation. -- 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] Reopened: (MCHECKSTYLE-105) Update to Checkstyle 5.0
[ http://jira.codehaus.org/browse/MCHECKSTYLE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof reopened MCHECKSTYLE-105: - > Update to Checkstyle 5.0 > > > Key: MCHECKSTYLE-105 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-105 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Felix Röthenbacher >Assignee: nicolas de loof > Fix For: 2.4 > > Attachments: patch.diff, update-to-5.0beta2.patch > > > Checkstyle 5.0-beta01 adds support for generics, etc. > See > http://checkstyle.sourceforge.net/5.x/releasenotes.html > for a list of new features. > Note: Prerequisite is that checkstyle-all jar, version 5.0-beta01 is > available from a public Maven repository. > Patch updates plugin to changed API / implementation. -- 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: (MCHECKSTYLE-110) option to output violations to the console when using chekstyle:check
[ http://jira.codehaus.org/browse/MCHECKSTYLE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MCHECKSTYLE-110. --- Assignee: nicolas de loof Resolution: Fixed Fix Version/s: 2.3 > option to output violations to the console when using chekstyle:check > - > > Key: MCHECKSTYLE-110 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-110 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: nicolas de loof >Assignee: nicolas de loof > Fix For: 2.3 > > > When chekstyle:check is used to validate project conventions during build, > the developer has to llok at the report XML file for violations. They should > be redirected to the console. -- 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: (MCHECKSTYLE-110) option to output violations to the console when using chekstyle:check
option to output violations to the console when using chekstyle:check - Key: MCHECKSTYLE-110 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-110 Project: Maven 2.x Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.3 Reporter: nicolas de loof When chekstyle:check is used to validate project conventions during build, the developer has to llok at the report XML file for violations. They should be redirected to the console. -- 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: (MCHECKSTYLE-105) Update to Checkstyle 5.0
[ http://jira.codehaus.org/browse/MCHECKSTYLE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MCHECKSTYLE-105. --- Assignee: nicolas de loof Resolution: Fixed Fix Version/s: 2.3 Fixed in SVN with update to Checkstyle 5.0 > Update to Checkstyle 5.0 > > > Key: MCHECKSTYLE-105 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-105 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Felix Röthenbacher >Assignee: nicolas de loof > Fix For: 2.3 > > Attachments: patch.diff, update-to-5.0beta2.patch > > > Checkstyle 5.0-beta01 adds support for generics, etc. > See > http://checkstyle.sourceforge.net/5.x/releasenotes.html > for a list of new features. > Note: Prerequisite is that checkstyle-all jar, version 5.0-beta01 is > available from a public Maven repository. > Patch updates plugin to changed API / implementation. -- 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: (MCHECKSTYLE-101) Skip should skip everything including the Velocity initialization
[
http://jira.codehaus.org/browse/MCHECKSTYLE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MCHECKSTYLE-101.
---
Resolution: Fixed
Fixed in SVN
> Skip should skip everything including the Velocity initialization
> -
>
> Key: MCHECKSTYLE-101
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-101
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Steve Gilbert
>Assignee: nicolas de loof
> Fix For: 2.3
>
>
> The "skip" configuration property prevents the check from happening, however,
> Velocity still gets initialized. For a small project, this takes the build
> time from 5 seconds without checkstyle in the pom to 13 seconds with it in
> and skip=true. While 8 seconds does not seem like much, it adds up over the
> course of days and weeks. Note that we have checkstyle hooked in at the
> verify/check phase/goal to cause the build to fail on a checkstyle violation
> during a typical developer's compilation they do all the time.
> Build output with skip=true:
> [INFO] Preparing checkstyle:check
> [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] **
> [INFO] Starting Jakarta Velocity v1.4
> [INFO] RuntimeInstance initializing.
> [INFO] Default Properties File:
> org\apache\velocity\runtime\defaults\velocity.properties
> [INFO] Default ResourceManager initializing. (class
> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> [INFO] Resource Loader Instantiated:
> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> [INFO] ClasspathResourceLoader : initialization starting.
> [INFO] ClasspathResourceLoader : initialization complete.
> [INFO] ResourceCache : initialized. (class
> org.apache.velocity.runtime.resource.ResourceCacheImpl)
> [INFO] Default ResourceManager initialization complete.
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
> [INFO] Created: 20 parsers.
> [INFO] Velocimacro : initialization starting.
> [INFO] Velocimacro : adding VMs from VM library template :
> VM_global_library.vm
> [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
> any resource loader.
> [INFO] Velocimacro : error using VM library template VM_global_library.vm :
> org.apache.velocity.exception.ResourceNotFoundException: Unable to find
> resource 'VM_global_library.vm'
> [INFO] Velocimacro : VM library template macro registration complete.
> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
> templates
> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [checkstyle:checkstyle]
> [INFO] [checkstyle:check {execution: default}]
> See also MCHECKSTYLE-71.
--
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] Reopened: (MCHECKSTYLE-101) Skip should skip everything including the Velocity initialization
[
http://jira.codehaus.org/browse/MCHECKSTYLE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof reopened MCHECKSTYLE-101:
-
Using Serviceable & ServiceLocator can avoid pre-configuration of the
VelocityComponent
> Skip should skip everything including the Velocity initialization
> -
>
> Key: MCHECKSTYLE-101
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-101
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Steve Gilbert
>Assignee: nicolas de loof
> Fix For: 2.3
>
>
> The "skip" configuration property prevents the check from happening, however,
> Velocity still gets initialized. For a small project, this takes the build
> time from 5 seconds without checkstyle in the pom to 13 seconds with it in
> and skip=true. While 8 seconds does not seem like much, it adds up over the
> course of days and weeks. Note that we have checkstyle hooked in at the
> verify/check phase/goal to cause the build to fail on a checkstyle violation
> during a typical developer's compilation they do all the time.
> Build output with skip=true:
> [INFO] Preparing checkstyle:check
> [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] **
> [INFO] Starting Jakarta Velocity v1.4
> [INFO] RuntimeInstance initializing.
> [INFO] Default Properties File:
> org\apache\velocity\runtime\defaults\velocity.properties
> [INFO] Default ResourceManager initializing. (class
> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> [INFO] Resource Loader Instantiated:
> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> [INFO] ClasspathResourceLoader : initialization starting.
> [INFO] ClasspathResourceLoader : initialization complete.
> [INFO] ResourceCache : initialized. (class
> org.apache.velocity.runtime.resource.ResourceCacheImpl)
> [INFO] Default ResourceManager initialization complete.
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
> [INFO] Created: 20 parsers.
> [INFO] Velocimacro : initialization starting.
> [INFO] Velocimacro : adding VMs from VM library template :
> VM_global_library.vm
> [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
> any resource loader.
> [INFO] Velocimacro : error using VM library template VM_global_library.vm :
> org.apache.velocity.exception.ResourceNotFoundException: Unable to find
> resource 'VM_global_library.vm'
> [INFO] Velocimacro : VM library template macro registration complete.
> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
> templates
> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [checkstyle:checkstyle]
> [INFO] [checkstyle:check {execution: default}]
> See also MCHECKSTYLE-71.
--
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: (MCHECKSTYLE-101) Skip should skip everything including the Velocity initialization
[
http://jira.codehaus.org/browse/MCHECKSTYLE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176305#action_176305
]
nicolas de loof commented on MCHECKSTYLE-101:
-
we use a shared plexus component that is dependency-injected by plexus
container.
What's wrong with this component beeing initialized ? only some undesirable
logs ?
> Skip should skip everything including the Velocity initialization
> -
>
> Key: MCHECKSTYLE-101
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-101
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Steve Gilbert
>Assignee: nicolas de loof
> Fix For: 2.3
>
>
> The "skip" configuration property prevents the check from happening, however,
> Velocity still gets initialized. For a small project, this takes the build
> time from 5 seconds without checkstyle in the pom to 13 seconds with it in
> and skip=true. While 8 seconds does not seem like much, it adds up over the
> course of days and weeks. Note that we have checkstyle hooked in at the
> verify/check phase/goal to cause the build to fail on a checkstyle violation
> during a typical developer's compilation they do all the time.
> Build output with skip=true:
> [INFO] Preparing checkstyle:check
> [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] **
> [INFO] Starting Jakarta Velocity v1.4
> [INFO] RuntimeInstance initializing.
> [INFO] Default Properties File:
> org\apache\velocity\runtime\defaults\velocity.properties
> [INFO] Default ResourceManager initializing. (class
> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> [INFO] Resource Loader Instantiated:
> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> [INFO] ClasspathResourceLoader : initialization starting.
> [INFO] ClasspathResourceLoader : initialization complete.
> [INFO] ResourceCache : initialized. (class
> org.apache.velocity.runtime.resource.ResourceCacheImpl)
> [INFO] Default ResourceManager initialization complete.
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
> [INFO] Created: 20 parsers.
> [INFO] Velocimacro : initialization starting.
> [INFO] Velocimacro : adding VMs from VM library template :
> VM_global_library.vm
> [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
> any resource loader.
> [INFO] Velocimacro : error using VM library template VM_global_library.vm :
> org.apache.velocity.exception.ResourceNotFoundException: Unable to find
> resource 'VM_global_library.vm'
> [INFO] Velocimacro : VM library template macro registration complete.
> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
> templates
> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [checkstyle:checkstyle]
> [INFO] [checkstyle:check {execution: default}]
> See also MCHECKSTYLE-71.
--
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: (MCHECKSTYLE-106) Unstable builds
[ http://jira.codehaus.org/browse/MCHECKSTYLE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MCHECKSTYLE-106. --- Resolution: Duplicate > Unstable builds > --- > > Key: MCHECKSTYLE-106 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-106 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.2 > Environment: Maven 2.0.9, Jdk 1.6.0_04, jdk 1.6.0_10, Linux (Centos4 > and Kubuntu 8.04) >Reporter: Johan Vogelzang > > Set up: > - Multimodule structure (one parent-pom and three submodules, one containing > our checkstyle configuration: smartjava_checks.xml) > - Checkstyle configuration as described in > http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html > - Command: mvn clean install site > The strange thing is that when run the exact same sources with the exact same > build goals multiple times, the build fails for about 50% of the times. When > the build fails it shows: > Embedded error: Error rendering Maven report: Unable to find configuration > file at location smartjava_checks.xml. > I have seen earlier issues about classloading problems related to this error, > but not this unstable behaviour. > Workaround: When you run the Maven command without "install" the build runs > successful. > mvn clean site -- 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: (MCHECKSTYLE-101) Skip should skip everything including the Velocity initialization
[
http://jira.codehaus.org/browse/MCHECKSTYLE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MCHECKSTYLE-101.
---
Assignee: nicolas de loof
Resolution: Won't Fix
Fix Version/s: 2.3
As the Velocity context is created from a plexus @component VelocityComponent,
we cannot check for skip parameter befor it get initialized.
> Skip should skip everything including the Velocity initialization
> -
>
> Key: MCHECKSTYLE-101
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-101
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Steve Gilbert
>Assignee: nicolas de loof
> Fix For: 2.3
>
>
> The "skip" configuration property prevents the check from happening, however,
> Velocity still gets initialized. For a small project, this takes the build
> time from 5 seconds without checkstyle in the pom to 13 seconds with it in
> and skip=true. While 8 seconds does not seem like much, it adds up over the
> course of days and weeks. Note that we have checkstyle hooked in at the
> verify/check phase/goal to cause the build to fail on a checkstyle violation
> during a typical developer's compilation they do all the time.
> Build output with skip=true:
> [INFO] Preparing checkstyle:check
> [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] **
> [INFO] Starting Jakarta Velocity v1.4
> [INFO] RuntimeInstance initializing.
> [INFO] Default Properties File:
> org\apache\velocity\runtime\defaults\velocity.properties
> [INFO] Default ResourceManager initializing. (class
> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> [INFO] Resource Loader Instantiated:
> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> [INFO] ClasspathResourceLoader : initialization starting.
> [INFO] ClasspathResourceLoader : initialization complete.
> [INFO] ResourceCache : initialized. (class
> org.apache.velocity.runtime.resource.ResourceCacheImpl)
> [INFO] Default ResourceManager initialization complete.
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
> [INFO] Created: 20 parsers.
> [INFO] Velocimacro : initialization starting.
> [INFO] Velocimacro : adding VMs from VM library template :
> VM_global_library.vm
> [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
> any resource loader.
> [INFO] Velocimacro : error using VM library template VM_global_library.vm :
> org.apache.velocity.exception.ResourceNotFoundException: Unable to find
> resource 'VM_global_library.vm'
> [INFO] Velocimacro : VM library template macro registration complete.
> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
> templates
> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [checkstyle:checkstyle]
> [INFO] [checkstyle:check {execution: default}]
> See also MCHECKSTYLE-71.
--
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: (MCHECKSTYLE-108) If I use the default maven checkstyle config, I can't use my own license header
[ http://jira.codehaus.org/browse/MCHECKSTYLE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MCHECKSTYLE-108. --- Assignee: nicolas de loof Resolution: Won't Fix Fix Version/s: 2.3 As described in MCHECKSTYLE-48, the maven_checks + LICENSE.txt combination is largelly used by maven for internal use, and to avoid regression we had to force the LICENSTE.txt to point to the default, common maven licence header. Simply changing your Licence file name / location to anything BUT "LICENSE.txt" will fix this. Beeing case sensitive, you could just rename it to "License.txt", or maybe LICENSE without "txt" extension > If I use the default maven checkstyle config, I can't use my own license > header > --- > > Key: MCHECKSTYLE-108 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-108 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Paul Gier >Assignee: nicolas de loof > Fix For: 2.3 > > > I'm working on a plugin that follows the maven code conventions, but uses the > MIT license instead of apache. If I set the configLocation to > "config/maven_checks.xml" then the plugin ignores the LICENSE.txt file that I > put into the root directory of my project even if I set the headerLocation. -- 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: (MCHECKSTYLE-109) Credentials ignored when provided in configLocation URL
[ http://jira.codehaus.org/browse/MCHECKSTYLE-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176292#action_176292 ] nicolas de loof commented on MCHECKSTYLE-109: - checkstyle plugin uses org.codehaus.plexus.resource.ResourceManager to convert configLocation to a File. > Credentials ignored when provided in configLocation URL > --- > > Key: MCHECKSTYLE-109 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-109 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.2 > Environment: maven 2.1.0 >Reporter: Stevo Slavic > > If configLocation URL contains username and password, e.g. > https://username:password/acme.org/checkstyle_checks.xml, those should be > used when obtaining checkstyle configuration xml. Currently, plugin fails to > obtain resource from such URL. -- 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-4151) Update maven API to use Java 5 generics
Update maven API to use Java 5 generics --- Key: MNG-4151 URL: http://jira.codehaus.org/browse/MNG-4151 Project: Maven 2 Issue Type: Task Components: IDEs Affects Versions: 2.2.x Reporter: nicolas de loof Priority: Trivial As Maven 2.2.x requires Java 5, upgrade maven API to use generics on collections. This will help plugin developers to avoid classCastException and make the API more comprehensible. -- 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: (SUREFIRE-508) cannot run GWTTestCases with surefire
[ http://jira.codehaus.org/browse/SUREFIRE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173433#action_173433 ] nicolas de loof commented on SUREFIRE-508: -- The command line limitation is blocking here. As GWT apps are web-layer they pull all project (business, persistence..) dependencies and get a long dependencies list. With maven repo path we end with CLASSPAHT far longer than the Windows XP 8191 chars limitation. > cannot run GWTTestCases with surefire > - > > Key: SUREFIRE-508 > URL: http://jira.codehaus.org/browse/SUREFIRE-508 > Project: Maven Surefire > Issue Type: Bug > Components: classloading >Affects Versions: 2.4.3 >Reporter: nicolas de loof > > GWTTestCase require some complex setup, as tje GWT compiler requires acces to > the java sources, and classpath scanning for available jars at runtime : > > maven-surefire-plugin > > > > src/main/java > > src/test/java > > target/generated-sources/gwt > > false > > > gwt.args > -out target/www-test > > > -Xmx256M > > > Even with this configuration, the test fails with a tomcat ClassCastException > "GWTShellServlet is not a Servlet" > I may be wrong, but it seems the useManifestOnlyJar=false mode still uses the > tmp file classpath elements to build it's classpath, and not the system > classpath. -- 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: (MWAR-187) regression running war packaging with maven 2.1
regression running war packaging with maven 2.1
---
Key: MWAR-187
URL: http://jira.codehaus.org/browse/MWAR-187
Project: Maven 2.x WAR Plugin
Issue Type: Bug
Affects Versions: 2.1-beta-1
Environment: Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100)
Java version: 1.6.0_11
Java home: D:\platina\java\jdk6\jre
Default locale: fr_FR, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Reporter: nicolas de loof
Priority: Minor
Using plugin version 2.1-beta-1, my webapp can't get packaged.
It can be fixed by downgrading the plugin to 2.0.2
{code}
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-war-plugin:2.1-beta-1:w
ar' -->
[DEBUG] (s) archiveClasses = false
[DEBUG] (s) attachClasses = false
[DEBUG] (s) cacheFile = D:\...\target\war\work\webapp-cache.xml
[DEBUG] (s) classesClassifier = classes
[DEBUG] (s) classesDirectory = D:\...\target\classes
[DEBUG] (f) escapedBackslashesInFilePath = false
[DEBUG] (s) failOnMissingWebXml = true
[DEBUG] (f) filteringDeploymentDescriptors = false
[DEBUG] (s) outputDirectory = D:\...\target
[DEBUG] (s) primaryArtifact = true
[DEBUG] (s) project = MavenProject: com.sfr.bios.pdc:bios-pdc-webservices:1.0.
0-SNAPSHOT @ D:\...\pom.xml
[DEBUG] (f) session = org.apache.maven.execution.mavensess...@10f0a0
[DEBUG] (s) useCache = true
[DEBUG] (s) warName = bios-pdc
[DEBUG] (s) warSourceDirectory = D:\...\src\main\webapp
[DEBUG] (s) webappDirectory =
D:\...\target\bios-pdc-webservices-1.0.0-SNAPSHOT
[DEBUG] (s) workDirectory = D:\...\target\war\work
[DEBUG] -- end configuration --
[INFO] [war:war]
[INFO] Packaging webapp
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] modelEncoding : modelEncoding : modelEncoding : modelEncoding
Debugging information
message : modelEncoding : modelEncoding
cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassExceptio
n
cause-message : modelEncoding : modelEncoding
class : org.apache.maven.plugin.war.util.WebappStructure
required-type : org.apache.maven.model.Dependency
path: /webapp-structure/dependenciesInfo/org.apache.maven.plugin
.war.util.DependencyInfo/dependency/modelEncoding
line number : 156
---
[INFO]
[INFO] Trace
com.thoughtworks.xstream.converters.ConversionException: modelEncoding : modelEn
coding : modelEncoding : modelEncoding
Debugging information
message : modelEncoding : modelEncoding
cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassExceptio
n
cause-message : modelEncoding : modelEncoding
class : org.apache.maven.plugin.war.util.WebappStructure
required-type : org.apache.maven.model.Dependency
path: /webapp-structure/dependenciesInfo/org.apache.maven.plugin
.war.util.DependencyInfo/dependency/modelEncoding
line number : 156
---
at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshall
er.java:89)
at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(A
bstractReferenceUnmarshaller.java:63)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnm
arshaller.java:76)
at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
erter.unmarshallField(AbstractReflectionConverter.java:246)
at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
erter.doUnmarshal(AbstractReflectionConverter.java:218)
at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConv
erter.unmarshal(AbstractReflectionConverter.java:162)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshall
er.java:82)
at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(A
bstractReferenceUnmarshaller.java:63)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnm
arshaller.java:76)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnm
arshaller.java:60)
at com.thoughtworks.xstream.converters.collections.AbstractCollectionCon
verter.readItem(AbstractCollectionConverter.java:71)
at com.thoughtworks.xstream.converters.collections.CollectionConverter.p
opulateCollection(CollectionConverter.java:68)
at com.thoughtworks.xstream.converters.collections.CollectionConverter.u
nmarshal(CollectionConverter.java:61)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshall
er.java:82)
at com.thoughtworks.xstream.core.AbstractReferen
[jira] Created: (ARCHETYPE-207) package with artifactId isn't replaced by archetype:generate
package with artifactId isn't replaced by archetype:generate
Key: ARCHETYPE-207
URL: http://jira.codehaus.org/browse/ARCHETYPE-207
Project: Maven Archetype
Issue Type: Bug
Affects Versions: 2.0-alpha-4
Reporter: nicolas de loof
Priority: Minor
On a multimodule project
(https://platina.svn.sourceforge.net/svnroot/platina/platina-archetype/trunk),
each module use as convention groupid + artifactid + module as package.
When used to create an archetype and the generate a new project, the generated
project still have the orinigal ("archetype") name as package, not the expected
new project artifactId.
sample :
original : com.capgemini.archetype.domain (project artifactId is "archetype")
actual : {groupid}.archetype.domain
expected : {groupid}.{artifactId}.domain
--
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-3722) Fail to run CXF code generation with 2.0.10 RC
Fail to run CXF code generation with 2.0.10 RC -- Key: MNG-3722 URL: http://jira.codehaus.org/browse/MNG-3722 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.10 Reporter: nicolas de loof Attachments: test.zip The attached project contains only a WSDL 2 Java code generation with a dependency to slf4j. Running "mvn install" fails in 2.0.10-RC9 with a NoSuchMethodError : trace on commons-logging SLF4J API. This MAY be a cxf plugin issue, as maybe it doesn't build the JAXB classpath correctly... Running with maven2 2.0.9 doesn't throw this error (the code generation fails as the sample WSDL is RPC/encoded, but this is not the issue to be demonstrated 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] Commented: (MNG-3691) When a snapshot is deployed with uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
[ http://jira.codehaus.org/browse/MNG-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144247#action_144247 ] nicolas de loof commented on MNG-3691: -- I understand well the snapshot usage with automatic updates when a new one is deployed. I dont undeerstand the use case of uniqueVersion=false if this is not to allow sort of "timestamp" version that ensure some reproductibility. To use such a timestamp, my POM needs to force all plugin SNAPSHOT dependencies versions. Maybe the enforcer and release plugins should also check for this when they accept a timestamp for a plugin or dependency > When a snapshot is deployed with uniqueVersion=false, it's SNAPSHOT > dependencies must be forced to timestamp > > > Key: MNG-3691 > URL: http://jira.codehaus.org/browse/MNG-3691 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 >Reporter: nicolas de loof > Fix For: Reviewed Pending Version Assignment > > > use case : > using the release plugin as a SNAPSHOT timestamped version to ensure > reproductibility. > When an incompatible SNAPSHOT of the release-manager is deployed, the plugin > doesn't work anymore : it updated it's SNAPSHOT dependencies. > -> uniqueVersion=false was useless to ensure reproductibility. > The isse is that the plugin POM has a SNAPSHOT dependency. As part of the > deploy process, the SNAPSHOT version SHOULD be forced to current timestamped > version to follow the uniqueVersion expectation. -- 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-3691) When a snapshot is deployed with uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp
When a snapshot is deployed with uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp Key: MNG-3691 URL: http://jira.codehaus.org/browse/MNG-3691 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Reporter: nicolas de loof use case : using the release plugin as a SNAPSHOT timestamped version to ensure reproductibility. When an incompatible SNAPSHOT of the release-manager is deployed, the plugin doesn't work anymore : it updated it's SNAPSHOT dependencies. -> uniqueVersion=false was useless to ensure reproductibility. The isse is that the plugin POM has a SNAPSHOT dependency. As part of the deploy process, the SNAPSHOT version SHOULD be forced to current timestamped version to follow the uniqueVersion expectation. -- 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: (SUREFIRE-508) cannot run GWTTestCases with surefire
cannot run GWTTestCases with surefire - Key: SUREFIRE-508 URL: http://jira.codehaus.org/browse/SUREFIRE-508 Project: Maven Surefire Issue Type: Bug Components: classloading Affects Versions: 2.4.3 Reporter: nicolas de loof GWTTestCase require some complex setup, as tje GWT compiler requires acces to the java sources, and classpath scanning for available jars at runtime : maven-surefire-plugin src/main/java src/test/java target/generated-sources/gwt false gwt.args -out target/www-test -Xmx256M Even with this configuration, the test fails with a tomcat ClassCastException "GWTShellServlet is not a Servlet" I may be wrong, but it seems the useManifestOnlyJar=false mode still uses the tmp file classpath elements to build it's classpath, and not the system classpath. -- 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: (MAVENUPLOAD-2119) please sync groupId com.etxjs with central
please sync groupId com.etxjs with central -- Key: MAVENUPLOAD-2119 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2119 Project: Maven Upload Requests Issue Type: Wish Reporter: nicolas de loof extjs provides support and enhancements for JavaScript and GWT web applications -- 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: (MAVENUPLOAD-2118) Please sync net.sf.gwt-widget groupId with central
Please sync net.sf.gwt-widget groupId with central -- Key: MAVENUPLOAD-2118 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2118 Project: Maven Upload Requests Issue Type: Wish Reporter: nicolas de loof -- 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-184) Fail to create multimodule archetype from project : modules created later as "__rootArtifactId__-modulename"
Fail to create multimodule archetype from project : modules created later as "__rootArtifactId__-modulename" Key: ARCHETYPE-184 URL: http://jira.codehaus.org/browse/ARCHETYPE-184 Project: Maven Archetype Issue Type: Bug Affects Versions: 2.0-alpha-3 Environment: creating multimodule archetype from project http://platina.svn.sourceforge.net/svnroot/platina/platina-archetype/trunk/ using the archetype.properties in SVN root Reporter: nicolas de loof Create archetype from project -> OK install -> OK generate -> NOK : __rootArtifactId__-application __rootArtifactId__-business __rootArtifactId__-domain __rootArtifactId__-infrastructure __rootArtifactId__-persistence __rootArtifactId__-remoting __rootArtifactId__-webapp __rootArtifactId__-webservices pom.xml All other elements are fine. -- 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: (MECLIPSE-437) Ordering of .classpath entries when using a newer version of JARs already included in the JDK.
[ http://jira.codehaus.org/browse/MECLIPSE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135524#action_135524 ] nicolas de loof commented on MECLIPSE-437: -- You're right this might be more configurable / extensible, but just consider this as a workaround waiting for eclipse to fix this. > Ordering of .classpath entries when using a newer version of JARs already > included in the JDK. > -- > > Key: MECLIPSE-437 > URL: http://jira.codehaus.org/browse/MECLIPSE-437 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.4 > Environment: WinXP, Maven 2.0.7 >Reporter: Patrick Zeising >Assignee: nicolas de loof > Fix For: 2.5.2 > > > While using a newer version of JaxWS (https://jax-ws.dev.java.net/) than the > one supplied with JDK6 the generated .classpath file in my project directory > contains all relevant entries headed by the entry for the JRE container. > ---CODE--- > > > > >path="M2_REPO/commons-lang/commons-lang/2.3/commons-lang-2.3.jar" > sourcepath="M2_REPO/commons-lang/commons-lang/2.3/commons-lang-2.3-sources.jar"/> > >path="M2_REPO/dev/java/net/jaxws-api/2.1.1/jaxws-api-2.1.1.jar"/> > >path="M2_REPO/commons-logging/commons-logging/1.1/commons-logging-1.1.jar" > sourcepath="M2_REPO/commons-logging/commons-logging/1.1/commons-logging-1.1-sources.jar"/> > > ---/CODE--- > As long as the JRE_CONTAINER is mentioned and loaded first my project will > not compile in Eclipse since I am using operations unique to the newer > version of JaxWS. When I set the order of the classpath entries in Eclipse > manually (Properties - Java Build Path - Order and Export, setting the entry > for JRE_CONTAINER to the 'bottom') my project will compile of course. > Nicolas de Loof suggested the following in my post to the maven users mailing > list > (http://www.nabble.com/Maven2-Eclipse-Plugin---ordering-of-.classpath-entries-p16722527s177.html): > ---CITE--- > Maybe the eclipse plugin could detect java* and javax* groupIds and force > them as toplevel ? > This would require : > - improve EclipseConfigWriter to have a new getJavaApiDeps(), and remove > those deps from getDepsOrdered > - improve EclipseClasspathWriter to write getJavaApiDeps prior to the JRE > container. > ---/CITE--- -- 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: (MECLIPSE-397) Eclipse project set as dependency + test-jar dependency is included twice in .classpath
[ http://jira.codehaus.org/browse/MECLIPSE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135512#action_135512 ] nicolas de loof commented on MECLIPSE-397: -- fixed in 2.5.2-20080520.120258-2 > Eclipse project set as dependency + test-jar dependency is included twice in > .classpath > --- > > Key: MECLIPSE-397 > URL: http://jira.codehaus.org/browse/MECLIPSE-397 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Workspace settings >Affects Versions: 2.5 > Environment: maven 2.0.8, eclipse plugin version > 2.5-20080218.113139-24 >Reporter: nicolas de loof >Assignee: nicolas de loof > Fix For: 2.5.2 > > > My maven project depends on A-util.jar for compile and A-util-tests.jar for > tests : > > ... > A-util > ... > > > ... > A-util > ... > test-jar > test > > I have the "A-util" project in my eclipse workspace > Running mvn eclipse:eclipse creates an invalid .classpath where the eclipse A > project is included twice : > > > .. and invalid .project with twice references : > A-util > A-util -- 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: (MECLIPSE-397) Eclipse project set as dependency + test-jar dependency is included twice in .classpath
[ http://jira.codehaus.org/browse/MECLIPSE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MECLIPSE-397. Assignee: nicolas de loof Resolution: Fixed Fix Version/s: 2.5.2 The issue comes from the anti-duplicates ID : String depId = dep.getGroupId() + ":" + dep.getArtifactId() + ":" + dep.getClassifier() + ":" + dep.getVersion(); For dependencies referenced as eclipse project, the same ID must be generated for any classifier / version. Also applied the anti-duplicate principle to .project writer. > Eclipse project set as dependency + test-jar dependency is included twice in > .classpath > --- > > Key: MECLIPSE-397 > URL: http://jira.codehaus.org/browse/MECLIPSE-397 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Workspace settings >Affects Versions: 2.5 > Environment: maven 2.0.8, eclipse plugin version > 2.5-20080218.113139-24 >Reporter: nicolas de loof >Assignee: nicolas de loof > Fix For: 2.5.2 > > > My maven project depends on A-util.jar for compile and A-util-tests.jar for > tests : > > ... > A-util > ... > > > ... > A-util > ... > test-jar > test > > I have the "A-util" project in my eclipse workspace > Running mvn eclipse:eclipse creates an invalid .classpath where the eclipse A > project is included twice : > > > .. and invalid .project with twice references : > A-util > A-util -- 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-341) support release process that use a staging repository
[ http://jira.codehaus.org/browse/MRELEASE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MRELEASE-341. Assignee: nicolas de loof Resolution: Fixed Fix Version/s: 2.0-beta-8 new release:stage Mojo with documentation > support release process that use a staging repository > - > > Key: MRELEASE-341 > URL: http://jira.codehaus.org/browse/MRELEASE-341 > Project: Maven 2.x Release Plugin > Issue Type: Improvement >Affects Versions: 2.0-beta-8 >Reporter: nicolas de loof >Assignee: nicolas de loof > Fix For: 2.0-beta-8 > > > Many release process (ex: geronimo) require the release candidate to be > exposed in a staging repository for testing, then vote from the communiity, > and finally copy the artifact in the public repository / web site. This > requires to run the release:perform with the final version (not a "-rc*" one). > When the vote fails, the release manager has to rollback the project to the > previous SNAPSHOT version. As release:perform removes all the release-related > files (including pom backups) the release:rollback goal cannot be used for > this. > Geronimo solution is to copy the trunk as a "savepoint" before staging a > release. A far better option would be to have a dedicated goal for this > "release:stage" : > * same features as release:perform > * don't remove release.properties and backups > * requires a stagingRepository parameter, to be passed as -DaltRepoLocation > to the deploy plugin > * detect the site:deploy goal and replace it with site:stage-deploy -- 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: (MRELEASE-341) support release process that use a staging repository
support release process that use a staging repository - Key: MRELEASE-341 URL: http://jira.codehaus.org/browse/MRELEASE-341 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-8 Reporter: nicolas de loof Many release process (ex: geronimo) require the release candidate to be exposed in a staging repository for testing, then vote from the communiity, and finally copy the artifact in the public repository / web site. This requires to run the release:perform with the final version (not a "-rc*" one). When the vote fails, the release manager has to rollback the project to the previous SNAPSHOT version. As release:perform removes all the release-related files (including pom backups) the release:rollback goal cannot be used for this. Geronimo solution is to copy the trunk as a "savepoint" before staging a release. A far better option would be to have a dedicated goal for this "release:stage" : * same features as release:perform * don't remove release.properties and backups * requires a stagingRepository parameter, to be passed as -DaltRepoLocation to the deploy plugin * detect the site:deploy goal and replace it with site:stage-deploy -- 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-3554) please grant me write acces to MAVEN space on wiki
[ http://jira.codehaus.org/browse/MNG-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MNG-3554. Resolution: Not A Bug > please grant me write acces to MAVEN space on wiki > -- > > Key: MNG-3554 > URL: http://jira.codehaus.org/browse/MNG-3554 > Project: Maven 2 > Issue Type: Wish >Reporter: nicolas de loof > > My maven committer Id is nicolas, but my codehaus confluence one is ndeloof. > Please give me write permision on MAVEN space. -- 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-3554) please grant me write acces to MAVEN space on wiki
please grant me write acces to MAVEN space on wiki -- Key: MNG-3554 URL: http://jira.codehaus.org/browse/MNG-3554 Project: Maven 2 Issue Type: Wish Reporter: nicolas de loof My maven committer Id is nicolas, but my codehaus confluence one is ndeloof. Please give me write permision on MAVEN space. -- 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: (MECLIPSE-437) Ordering of .classpath entries when using a newer version of JARs already included in the JDK.
[ http://jira.codehaus.org/browse/MECLIPSE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132834#action_132834 ] nicolas de loof commented on MECLIPSE-437: -- I've reported this issue to eclipse : https://bugs.eclipse.org/bugs/show_bug.cgi?id=228488 The current fix on .classpath ordering is only a workaround. > Ordering of .classpath entries when using a newer version of JARs already > included in the JDK. > -- > > Key: MECLIPSE-437 > URL: http://jira.codehaus.org/browse/MECLIPSE-437 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.4 > Environment: WinXP, Maven 2.0.7 >Reporter: Patrick Zeising >Assignee: nicolas de loof > Fix For: 2.5.2 > > > While using a newer version of JaxWS (https://jax-ws.dev.java.net/) than the > one supplied with JDK6 the generated .classpath file in my project directory > contains all relevant entries headed by the entry for the JRE container. > ---CODE--- > > > > >path="M2_REPO/commons-lang/commons-lang/2.3/commons-lang-2.3.jar" > sourcepath="M2_REPO/commons-lang/commons-lang/2.3/commons-lang-2.3-sources.jar"/> > >path="M2_REPO/dev/java/net/jaxws-api/2.1.1/jaxws-api-2.1.1.jar"/> > >path="M2_REPO/commons-logging/commons-logging/1.1/commons-logging-1.1.jar" > sourcepath="M2_REPO/commons-logging/commons-logging/1.1/commons-logging-1.1-sources.jar"/> > > ---/CODE--- > As long as the JRE_CONTAINER is mentioned and loaded first my project will > not compile in Eclipse since I am using operations unique to the newer > version of JaxWS. When I set the order of the classpath entries in Eclipse > manually (Properties - Java Build Path - Order and Export, setting the entry > for JRE_CONTAINER to the 'bottom') my project will compile of course. > Nicolas de Loof suggested the following in my post to the maven users mailing > list > (http://www.nabble.com/Maven2-Eclipse-Plugin---ordering-of-.classpath-entries-p16722527s177.html): > ---CITE--- > Maybe the eclipse plugin could detect java* and javax* groupIds and force > them as toplevel ? > This would require : > - improve EclipseConfigWriter to have a new getJavaApiDeps(), and remove > those deps from getDepsOrdered > - improve EclipseClasspathWriter to write getJavaApiDeps prior to the JRE > container. > ---/CITE--- -- 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: (MENFORCER-44) the banSnapshot option in requirePluginVersions should distinguish "SNAPSHOT" and timestamps
[ http://jira.codehaus.org/browse/MENFORCER-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MENFORCER-44. Assignee: nicolas de loof (was: Brian Fox) Resolution: Fixed Fix Version/s: 1.0 banTimestamps = false allow to user timestamp SNAPSHOTS (as release plugin does) > the banSnapshot option in requirePluginVersions should distinguish "SNAPSHOT" > and timestamps > > > Key: MENFORCER-44 > URL: http://jira.codehaus.org/browse/MENFORCER-44 > Project: Maven 2.x Enforcer Plugin > Issue Type: Improvement > Components: Standard Rules >Affects Versions: 1.0 >Reporter: nicolas de loof >Assignee: nicolas de loof > Fix For: 1.0 > > > The release plugin now allows to use timestamp dependencies. > the requirePluginVersions rule cannot be used with such configuration as it > considers a timestamp as a SNAPSHOT. > Maybe the SNAPSHOT detection code could be shared ? -- 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: (MENFORCER-45) does not detect version for plugin configured in profiles
[ http://jira.codehaus.org/browse/MENFORCER-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MENFORCER-45. Resolution: Fixed Fix Version/s: 1.0 Add all plugins in profiles as candidates for version check > does not detect version for plugin configured in profiles > - > > Key: MENFORCER-45 > URL: http://jira.codehaus.org/browse/MENFORCER-45 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Affects Versions: 1.0 >Reporter: nicolas de loof >Assignee: nicolas de loof > Fix For: 1.0 > > > Here is my POM.xml : > ... > > > cxf > > true > > > > > org.apache.cxf > cxf-codegen-plugin > 2.05.-incubator > ... > [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequirePluginVersions > failed with message: > Some plugins are missing valid versions:(LATEST RELEASE are not allowed ) > org.apache.cxf:cxf-codegen-plugin. The version currently in use is > 2.0.5-incubator -- 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: (MENFORCER-45) does not detect version for plugin configured in profiles
does not detect version for plugin configured in profiles - Key: MENFORCER-45 URL: http://jira.codehaus.org/browse/MENFORCER-45 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Components: Standard Rules Affects Versions: 1.0 Reporter: nicolas de loof Assignee: Brian Fox Here is my POM.xml : ... cxf true org.apache.cxf cxf-codegen-plugin 2.05.-incubator ... [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequirePluginVersions failed with message: Some plugins are missing valid versions:(LATEST RELEASE are not allowed ) org.apache.cxf:cxf-codegen-plugin. The version currently in use is 2.0.5-incubator -- 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: (MENFORCER-44) the banSnapshot option in requirePluginVersions should distinguish "SNAPSHOT" and timestamps
the banSnapshot option in requirePluginVersions should distinguish "SNAPSHOT" and timestamps Key: MENFORCER-44 URL: http://jira.codehaus.org/browse/MENFORCER-44 Project: Maven 2.x Enforcer Plugin Issue Type: Improvement Components: Standard Rules Affects Versions: 1.0 Reporter: nicolas de loof Assignee: Brian Fox The release plugin now allows to use timestamp dependencies. the requirePluginVersions rule cannot be used with such configuration as it considers a timestamp as a SNAPSHOT. Maybe the SNAPSHOT detection code could be shared ? -- 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: (MECLIPSE-440) unit tests depends on local configuration and artifacts in local repository
unit tests depends on local configuration and artifacts in local repository --- Key: MECLIPSE-440 URL: http://jira.codehaus.org/browse/MECLIPSE-440 Project: Maven 2.x Eclipse Plugin Issue Type: Task Components: Core : Workspace settings Affects Versions: 2.5.2 Reporter: nicolas de loof My local repository contans -sources.jar for junit and servlet-api. I then have failing tests : testProject13(org.apache.maven.plugin.eclipse.EclipsePluginTest) testProject22(org.apache.maven.plugin.eclipse.EclipsePluginTest) testProject28(org.apache.maven.plugin.eclipse.EclipsePluginTest) testProject29(org.apache.maven.plugin.eclipse.EclipsePluginTest) testProject30(org.apache.maven.plugin.eclipse.EclipsePluginTest) ... All of them fail beacuse the .classpath contains link to the sources archive : Checking .classpath, line #3 expected:<...servlet-api-2.3.jar"[]/>> but was:<...servlet-api-2.3.jar"[ sourcepath="M2_REPO/javax/servlet/servlet-api/2.3/servlet-api-2.3-sources.jar"]/>> An option would be to package with the plugin test resource a repository containing fake (0byte) artifacts, and use it as local repo with offline mode set, so that the available artifacts are fully under control. -- 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: (MECLIPSE-437) Ordering of .classpath entries when using a newer version of JARs already included in the JDK.
[ http://jira.codehaus.org/browse/MECLIPSE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MECLIPSE-437. Assignee: nicolas de loof Resolution: Fixed Fix Version/s: 2.5.2 added IdeDependency.isJavaApi() based on java.* / javax.* groupIds changed EclipseClassPathWriter to write javaApi dependency prior to classpath container. TODO : maybe some better discovery mecanism could also include "geronimo-specs-*" and equivalent jars by opening the dependency .jar and looking for java.*/javax.* packages, but this would slow the plugin. > Ordering of .classpath entries when using a newer version of JARs already > included in the JDK. > -- > > Key: MECLIPSE-437 > URL: http://jira.codehaus.org/browse/MECLIPSE-437 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.4 > Environment: WinXP, Maven 2.0.7 >Reporter: Patrick Zeising >Assignee: nicolas de loof > Fix For: 2.5.2 > > > While using a newer version of JaxWS (https://jax-ws.dev.java.net/) than the > one supplied with JDK6 the generated .classpath file in my project directory > contains all relevant entries headed by the entry for the JRE container. > ---CODE--- > > > > >path="M2_REPO/commons-lang/commons-lang/2.3/commons-lang-2.3.jar" > sourcepath="M2_REPO/commons-lang/commons-lang/2.3/commons-lang-2.3-sources.jar"/> > >path="M2_REPO/dev/java/net/jaxws-api/2.1.1/jaxws-api-2.1.1.jar"/> > >path="M2_REPO/commons-logging/commons-logging/1.1/commons-logging-1.1.jar" > sourcepath="M2_REPO/commons-logging/commons-logging/1.1/commons-logging-1.1-sources.jar"/> > > ---/CODE--- > As long as the JRE_CONTAINER is mentioned and loaded first my project will > not compile in Eclipse since I am using operations unique to the newer > version of JaxWS. When I set the order of the classpath entries in Eclipse > manually (Properties - Java Build Path - Order and Export, setting the entry > for JRE_CONTAINER to the 'bottom') my project will compile of course. > Nicolas de Loof suggested the following in my post to the maven users mailing > list > (http://www.nabble.com/Maven2-Eclipse-Plugin---ordering-of-.classpath-entries-p16722527s177.html): > ---CITE--- > Maybe the eclipse plugin could detect java* and javax* groupIds and force > them as toplevel ? > This would require : > - improve EclipseConfigWriter to have a new getJavaApiDeps(), and remove > those deps from getDepsOrdered > - improve EclipseClasspathWriter to write getJavaApiDeps prior to the JRE > container. > ---/CITE--- -- 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-337) generated command line must remove newLine characters
[ http://jira.codehaus.org/browse/MRELEASE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MRELEASE-337. Resolution: Fixed fixed in 2.0-beta-8-20080418.064928-4 > generated command line must remove newLine characters > - > > Key: MRELEASE-337 > URL: http://jira.codehaus.org/browse/MRELEASE-337 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-8 >Reporter: nicolas de loof >Assignee: nicolas de loof > Fix For: 2.0-beta-8 > > > When using an XML editor with formating support, a long goal list (including > custom plugins with com.mycompany.groupId:plugin:goal) MAY be splitted into > multiple lines. > The release:perform executed command line does not remove such new lines > characters, and some options / goals are not passed to the mvn instance -- 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] Reopened: (MRELEASE-337) generated command line must remove newLine characters
[ http://jira.codehaus.org/browse/MRELEASE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof reopened MRELEASE-337: -- Will fix this ASAP. thanks for reporting... > generated command line must remove newLine characters > - > > Key: MRELEASE-337 > URL: http://jira.codehaus.org/browse/MRELEASE-337 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-8 >Reporter: nicolas de loof >Assignee: nicolas de loof > Fix For: 2.0-beta-8 > > > When using an XML editor with formating support, a long goal list (including > custom plugins with com.mycompany.groupId:plugin:goal) MAY be splitted into > multiple lines. > The release:perform executed command line does not remove such new lines > characters, and some options / goals are not passed to the mvn instance -- 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-337) generated command line must remove newLine characters
[ http://jira.codehaus.org/browse/MRELEASE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MRELEASE-337. Resolution: Fixed Fix Version/s: 2.0-beta-8 goals parameter is now splitted and joined to produce a single line command > generated command line must remove newLine characters > - > > Key: MRELEASE-337 > URL: http://jira.codehaus.org/browse/MRELEASE-337 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-8 >Reporter: nicolas de loof >Assignee: nicolas de loof > Fix For: 2.0-beta-8 > > > When using an XML editor with formating support, a long goal list (including > custom plugins with com.mycompany.groupId:plugin:goal) MAY be splitted into > multiple lines. > The release:perform executed command line does not remove such new lines > characters, and some options / goals are not passed to the mvn instance -- 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] Work started: (MRELEASE-337) generated command line must remove newLine characters
[ http://jira.codehaus.org/browse/MRELEASE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRELEASE-337 started by nicolas de loof. > generated command line must remove newLine characters > - > > Key: MRELEASE-337 > URL: http://jira.codehaus.org/browse/MRELEASE-337 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-8 >Reporter: nicolas de loof >Assignee: nicolas de loof > > When using an XML editor with formating support, a long goal list (including > custom plugins with com.mycompany.groupId:plugin:goal) MAY be splitted into > multiple lines. > The release:perform executed command line does not remove such new lines > characters, and some options / goals are not passed to the mvn instance -- 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: (MRELEASE-337) generated command line must remove newLine characters
generated command line must remove newLine characters - Key: MRELEASE-337 URL: http://jira.codehaus.org/browse/MRELEASE-337 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-8 Reporter: nicolas de loof When using an XML editor with formating support, a long goal list (including custom plugins with com.mycompany.groupId:plugin:goal) MAY be splitted into multiple lines. The release:perform executed command line does not remove such new lines characters, and some options / goals are not passed to the mvn instance -- 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-1995) Please sync javassist groupId
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129892#action_129892 ] nicolas de loof commented on MAVENUPLOAD-1995: -- according to maven-meeper CSV file, there is an unexpecetd trailing " " for javassist groupId "javassist ","[EMAIL PROTECTED]:/home/nicolas/rsync-to-central","rsync_ssh","Nicolas De Loof","[EMAIL PROTECTED]",," " > Please sync javassist groupId > - > > Key: MAVENUPLOAD-1995 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1995 > Project: maven-upload-requests > Issue Type: Task >Reporter: nicolas de loof >Assignee: Carlos Sanchez > > This is only a copy of http://repository.jboss.com/maven2/javassist/ > If there is a better way to sync some artifacts from > http://repository.jboss.com to central please let me know -- 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] Reopened: (MAVENUPLOAD-1995) Please sync javassist groupId
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof reopened MAVENUPLOAD-1995: -- Content from people.apache.org/x1/home/nicolas/rsync-to-central/javassist isn't copied to repo1.maven.org/maven2/javassist I've added versions 3.6.0.GA and 3.7.1.GA and see nothing on central. > Please sync javassist groupId > - > > Key: MAVENUPLOAD-1995 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1995 > Project: maven-upload-requests > Issue Type: Task >Reporter: nicolas de loof >Assignee: Carlos Sanchez > > This is only a copy of http://repository.jboss.com/maven2/javassist/ > If there is a better way to sync some artifacts from > http://repository.jboss.com to central please let me know -- 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-1984) please upload scannotations
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129275#action_129275 ] nicolas de loof commented on MAVENUPLOAD-1984: -- As described, the bundle was created using the original project POM. I've repackaged it as a sync folder, with a modified POM to use groupId net.sf.scannotation and remove unexpected jboss repository Please sync "net.sf.scannotation","[EMAIL PROTECTED]:/home/nicolas/rsync-to-central","rsync_ssh","Nicolas De Loof","[EMAIL PROTECTED]",, > please upload scannotations > --- > > Key: MAVENUPLOAD-1984 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1984 > Project: maven-upload-requests > Issue Type: Task >Reporter: nicolas de loof > > Scannotation allow to retrieve a set of annotated classes from classpath > This bundle was create from the project POM.xml, with addition for required > metadatas to build the bundle. -- 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: (MAVENUPLOAD-1995) Please sync javassist groupId
Please sync javassist groupId - Key: MAVENUPLOAD-1995 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1995 Project: maven-upload-requests Issue Type: Task Reporter: nicolas de loof This is only a copy of http://repository.jboss.com/maven2/javassist/ If there is a better way to sync some artifacts from http://repository.jboss.com to central please let me know -- 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: (MAVENUPLOAD-1992) Please sync org.jsdoctoolkit groupId with central
Please sync org.jsdoctoolkit groupId with central - Key: MAVENUPLOAD-1992 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1992 Project: maven-upload-requests Issue Type: Task Reporter: nicolas de loof -- 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: (MECLIPSE-414) Not beeing @aggregator, eclipse plugin does not require executedProject
Not beeing @aggregator, eclipse plugin does not require executedProject
---
Key: MECLIPSE-414
URL: http://jira.codehaus.org/browse/MECLIPSE-414
Project: Maven 2.x Eclipse Plugin
Issue Type: Wish
Affects Versions: 2.5
Reporter: nicolas de loof
Priority: Minor
The eclispe plugin uses both ${executedProject} and ${project}.
Not beeing an aggregator plugin, ${project} is allways tghe currently executed
project, and the projectDirectory is project.getBasedir().
Having two attributes for same target makes the plugin harder to understand
--
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: (MAVENUPLOAD-1984) please upload scannotations
please upload scannotations --- Key: MAVENUPLOAD-1984 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1984 Project: maven-upload-requests Issue Type: Task Reporter: nicolas de loof Scannotation allow to retrieve a set of annotated classes from classpath This bundle was create from the project POM.xml, with addition for required metadatas to build the bundle. -- 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-1971) Please sync com.capgemini.platina groupId with central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128653#action_128653 ] nicolas de loof commented on MAVENUPLOAD-1971: -- According to http://svn.apache.org/repos/asf/maven/archiva/tools/trunk/maven-meeper/src/bin/synchronize/m2-sync/sync.csv my sync script has a %!$#!! windows-style EOL for the repository folder name, that breaks the configuration > Please sync com.capgemini.platina groupId with central > -- > > Key: MAVENUPLOAD-1971 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1971 > Project: maven-upload-requests > Issue Type: Wish >Reporter: nicolas de loof >Assignee: Carlos Sanchez > Attachments: platina.sh > > > I've created for my company (capgemini) some maven components and corporate > POM. > They're distributed under apache license, so I'd like them to get deployed on > central. -- 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] Reopened: (MAVENUPLOAD-1971) Please sync com.capgemini.platina groupId with central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof reopened MAVENUPLOAD-1971: -- I receive warning from the sync process : Seems the groupId directory should not have a trailing "/" Can you fix this please ? --- Some repositories were not synchronized --- groupId: com.capgemini.platina Error: /bin/sh: line 1: /com/capgemini/platina/: No such file or directory Error synchronizing metadata. Exit code: 127 This is an automated email, do not respond.Contact the owners at [EMAIL PROTECTED] > Please sync com.capgemini.platina groupId with central > -- > > Key: MAVENUPLOAD-1971 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1971 > Project: maven-upload-requests > Issue Type: Wish >Reporter: nicolas de loof >Assignee: Carlos Sanchez > Attachments: platina.sh > > > I've created for my company (capgemini) some maven components and corporate > POM. > They're distributed under apache license, so I'd like them to get deployed on > central. -- 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: (MAVENUPLOAD-1982) Please sync net.sf.hibernate4gwt groupId with central
Please sync net.sf.hibernate4gwt groupId with central - Key: MAVENUPLOAD-1982 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1982 Project: maven-upload-requests Issue Type: Wish Reporter: nicolas de loof -- 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-1972) please upload GWT 1.4.62
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128308#action_128308 ] nicolas de loof commented on MAVENUPLOAD-1972: -- Right, so please sync com.google.gwt groupId from : "com.google.gwt","[EMAIL PROTECTED]:/home/nicolas/rsync-to-central","rsync_ssh","Nicolas De Loof","[EMAIL PROTECTED]",, > please upload GWT 1.4.62 > > > Key: MAVENUPLOAD-1972 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1972 > Project: maven-upload-requests > Issue Type: Wish >Reporter: nicolas de loof > > Google guys just released GWT 1.4.62 > (http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/bd5cbb7a0d5b60aa/b85b6c2157aa26cb) > I'd like to update the codehaus GWT plugin to use this version > The bundle contains server and runtime jars + development jars for windows, > linux, mac and macOS leopard -- 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: (MAVENUPLOAD-1972) please upload GWT 1.4.62
please upload GWT 1.4.62 Key: MAVENUPLOAD-1972 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1972 Project: maven-upload-requests Issue Type: Wish Reporter: nicolas de loof Google guys just released GWT 1.4.62 (http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/bd5cbb7a0d5b60aa/b85b6c2157aa26cb) I'd like to update the codehaus GWT plugin to use this version The bundle contains server and runtime jars + development jars for windows, linux, mac and macOS leopard -- 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: (MAVENUPLOAD-1971) Please sync com.capgemini.platina groupId with central
Please sync com.capgemini.platina groupId with central -- Key: MAVENUPLOAD-1971 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1971 Project: maven-upload-requests Issue Type: Wish Reporter: nicolas de loof Attachments: platina.sh I've created for my company (capgemini) some maven components and corporate POM. They're distributed under apache license, so I'd like them to get deployed on central. -- 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: (MASSEMBLY-299) assembly does not honnor directives
assembly does not honnor directives -- Key: MASSEMBLY-299 URL: http://jira.codehaus.org/browse/MASSEMBLY-299 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-2 Reporter: nicolas de loof My project uses many libs and has set to force commons-logging on version 1.1.1 I still have commons-logging 1.1 in my assembly targ.gz, (with its dependencies : logkit, avalon ...) Forcing a dependency to commons-logging 1.1.1 solves this, but this is just a workaround. As the assembly plugin uses "dependencyResolver.resolveDependencies( project, ... " we could expect the dependencyResolver to read the , but this doesn't seem to work as expected. -- 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: (MECLIPSE-397) Eclipse project set as dependency + test-jar dependency is included twice in .classpath
[ http://jira.codehaus.org/browse/MECLIPSE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126450 ] nicolas de loof commented on MECLIPSE-397: -- Issue is a little more complex. When eclipse .classpath make reference to project A-util, it only includes default build directory (target/classes), so will never include the target/test-classes that matches the A-util-tests.jar. I don't know if this is possible to specify build directory in target project in the .classpath XML format. The UI editor doesn't provides this option. > Eclipse project set as dependency + test-jar dependency is included twice in > .classpath > --- > > Key: MECLIPSE-397 > URL: http://jira.codehaus.org/browse/MECLIPSE-397 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Workspace settings >Affects Versions: 2.5 > Environment: maven 2.0.8, eclipse plugin version > 2.5-20080218.113139-24 >Reporter: nicolas de loof > > My maven project depends on A-util.jar for compile and A-util-tests.jar for > tests : > > ... > A-util > ... > > > ... > A-util > ... > test-jar > test > > I have the "A-util" project in my eclipse workspace > Running mvn eclipse:eclipse creates an invalid .classpath where the eclipse A > project is included twice : > > > .. and invalid .project with twice references : > A-util > A-util -- 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: (MECLIPSE-397) Eclipse project set as dependency + test-jar dependency is included twice in .classpath
[ http://jira.codehaus.org/browse/MECLIPSE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof updated MECLIPSE-397: - Description: My maven project depends on A-util.jar for compile and A-util-tests.jar for tests : ... A-util ... ... A-util ... test-jar test I have the "A-util" project in my eclipse workspace Running mvn eclipse:eclipse creates an invalid .classpath where the eclipse A project is included twice : .. and invalid .project with twice references : A-util A-util was: My maven project depends on A-util.jar for compile and A-util-tests.jar for tests : ... A-util ... ... A-util ... test-jar test I have the "A-util" project in my eclipse workspace Running mvn eclipse:eclipse creates an invalid .classpath where the eclipse A project is included twice : > Eclipse project set as dependency + test-jar dependency is included twice in > .classpath > --- > > Key: MECLIPSE-397 > URL: http://jira.codehaus.org/browse/MECLIPSE-397 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Workspace settings >Affects Versions: 2.5 > Environment: maven 2.0.8, eclipse plugin version > 2.5-20080218.113139-24 >Reporter: nicolas de loof > > My maven project depends on A-util.jar for compile and A-util-tests.jar for > tests : > > ... > A-util > ... > > > ... > A-util > ... > test-jar > test > > I have the "A-util" project in my eclipse workspace > Running mvn eclipse:eclipse creates an invalid .classpath where the eclipse A > project is included twice : > > > .. and invalid .project with twice references : > A-util > A-util -- 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: (MECLIPSE-397) Eclipse project set as dependency + test-jar dependency is included twice in .classpath
[ http://jira.codehaus.org/browse/MECLIPSE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof updated MECLIPSE-397: - Summary: Eclipse project set as dependency + test-jar dependency is included twice in .classpath (was: Eclipse project set as dependency + test-jar dependency i sincluded twice in .classpath) > Eclipse project set as dependency + test-jar dependency is included twice in > .classpath > --- > > Key: MECLIPSE-397 > URL: http://jira.codehaus.org/browse/MECLIPSE-397 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Workspace settings >Affects Versions: 2.5 > Environment: maven 2.0.8, eclipse plugin version > 2.5-20080218.113139-24 >Reporter: nicolas de loof > > My maven project depends on A-util.jar for compile and A-util-tests.jar for > tests : > > ... > A-util > ... > > > ... > A-util > ... > test-jar > test > > I have the "A-util" project in my eclipse workspace > Running mvn eclipse:eclipse creates an invalid .classpath where the eclipse A > project is included twice : > > -- 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: (MECLIPSE-397) Eclipse project set as dependency + test-jar dependency i sincluded twice in .classpath
Eclipse project set as dependency + test-jar dependency i sincluded twice in .classpath --- Key: MECLIPSE-397 URL: http://jira.codehaus.org/browse/MECLIPSE-397 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Workspace settings Affects Versions: 2.5 Environment: maven 2.0.8, eclipse plugin version 2.5-20080218.113139-24 Reporter: nicolas de loof My maven project depends on A-util.jar for compile and A-util-tests.jar for tests : ... A-util ... ... A-util ... test-jar test I have the "A-util" project in my eclipse workspace Running mvn eclipse:eclipse creates an invalid .classpath where the eclipse A project is included twice : -- 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-3426) regression : in plugin configuration doesn't override plugin classpath
[ http://jira.codehaus.org/browse/MNG-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MNG-3426. Assignee: nicolas de loof Resolution: Fixed Fix Version/s: 2.0.9 Use a LinkedHashSet to make plugin dependencies ordering predictable (same as maven 2.1) and place project.build.plugin.dependencies prior to plugin POM dependencies > regression : in plugin configuration doesn't override plugin > classpath > --- > > Key: MNG-3426 > URL: http://jira.codehaus.org/browse/MNG-3426 > Project: Maven 2 > Issue Type: Bug > Components: Plugin API >Affects Versions: 2.0.8 >Reporter: nicolas de loof >Assignee: nicolas de loof >Priority: Critical > Fix For: 2.0.9 > > > Many maven plugins are wrapper around other tools. The plugin is designed for > a version of the tool, and in many case user will want to use a specific > version without having to patch the plugin. The element on > plugin configuration is a common way to do this, by overriding the plugin POM > dependency with another version. > >castor-maven-plugin > > > org.codehaus.castor > castor > VERSION OF CASTOR I WANT TO USE FOR CODE > GENERATION > > > > This used to work with maven < 2.0.8 > In maven 2.0.8, this doesn't work anymore as the set in plugin > configuration is added to plugin classpath, as a duplicate for the one > declared by the plugin but LATER in the classpath (but I may be wrong on this > analysis). -- 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-3426) regression : in plugin configuration doesn't override plugin classpath
[ http://jira.codehaus.org/browse/MNG-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125869 ] nicolas de loof commented on MNG-3426: -- testcase committed in maven\core-integration-testing\core-integration-tests testcase uses castor-maven-plugin as castor codegen includes castor version in generated files header on maven 2.0.8, generated code is always for 1.1.2.1, as specified by plugin dependencies, even when is set on plugin configuration. > regression : in plugin configuration doesn't override plugin > classpath > --- > > Key: MNG-3426 > URL: http://jira.codehaus.org/browse/MNG-3426 > Project: Maven 2 > Issue Type: Bug > Components: Plugin API >Affects Versions: 2.0.8 >Reporter: nicolas de loof >Priority: Critical > > Many maven plugins are wrapper around other tools. The plugin is designed for > a version of the tool, and in many case user will want to use a specific > version without having to patch the plugin. The element on > plugin configuration is a common way to do this, by overriding the plugin POM > dependency with another version. > >castor-maven-plugin > > > org.codehaus.castor > castor > VERSION OF CASTOR I WANT TO USE FOR CODE > GENERATION > > > > This used to work with maven < 2.0.8 > In maven 2.0.8, this doesn't work anymore as the set in plugin > configuration is added to plugin classpath, as a duplicate for the one > declared by the plugin but LATER in the classpath (but I may be wrong on this > analysis). -- 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-3426) regression : in plugin configuration doesn't override plugin classpath
[ http://jira.codehaus.org/browse/MNG-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125863 ] nicolas de loof commented on MNG-3426: -- Yes, I plan to both provide a test case and investigate to fix this in 2.0.9. > regression : in plugin configuration doesn't override plugin > classpath > --- > > Key: MNG-3426 > URL: http://jira.codehaus.org/browse/MNG-3426 > Project: Maven 2 > Issue Type: Bug > Components: Plugin API >Affects Versions: 2.0.8 >Reporter: nicolas de loof >Priority: Critical > > Many maven plugins are wrapper around other tools. The plugin is designed for > a version of the tool, and in many case user will want to use a specific > version without having to patch the plugin. The element on > plugin configuration is a common way to do this, by overriding the plugin POM > dependency with another version. > >castor-maven-plugin > > > org.codehaus.castor > castor > VERSION OF CASTOR I WANT TO USE FOR CODE > GENERATION > > > > This used to work with maven < 2.0.8 > In maven 2.0.8, this doesn't work anymore as the set in plugin > configuration is added to plugin classpath, as a duplicate for the one > declared by the plugin but LATER in the classpath (but I may be wrong on this > analysis). -- 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: (MNG-3426) regression : in plugin configuration doesn't override plugin classpath
[ http://jira.codehaus.org/browse/MNG-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof updated MNG-3426: - Description: Many maven plugins are wrapper around other tools. The plugin is designed for a version of the tool, and in many case user will want to use a specific version without having to patch the plugin. The element on plugin configuration is a common way to do this, by overriding the plugin POM dependency with another version. castor-maven-plugin org.codehaus.castor castor VERSION OF CASTOR I WANT TO USE FOR CODE GENERATION This used to work with maven < 2.0.8 In maven 2.0.8, this doesn't work anymore as the set in plugin configuration is added to plugin classpath, as a duplicate for the one declared by the plugin but LATER in the classpath (but I may be wrong on this analysis). was: Many maven plugins are wrapper around other tools. The plugin is designed for a version of the tool, and in many case user will want to use a specific version without having to patch the plugin. The element on plugin configuration is a common way to do this, by overriding the plugin POM dependency with another version. This used to work with maven < 2.0.8 In maven 2.0.8, this doesn't work anomire as the set in plugin configuration is added to classpath, as a duplicate for the on declared by the plugin but LATER in the classpath. > regression : in plugin configuration doesn't override plugin > classpath > --- > > Key: MNG-3426 > URL: http://jira.codehaus.org/browse/MNG-3426 > Project: Maven 2 > Issue Type: Bug > Components: Plugin API >Affects Versions: 2.0.8 >Reporter: nicolas de loof >Priority: Critical > > Many maven plugins are wrapper around other tools. The plugin is designed for > a version of the tool, and in many case user will want to use a specific > version without having to patch the plugin. The element on > plugin configuration is a common way to do this, by overriding the plugin POM > dependency with another version. > >castor-maven-plugin > > > org.codehaus.castor > castor > VERSION OF CASTOR I WANT TO USE FOR CODE > GENERATION > > > > This used to work with maven < 2.0.8 > In maven 2.0.8, this doesn't work anymore as the set in plugin > configuration is added to plugin classpath, as a duplicate for the one > declared by the plugin but LATER in the classpath (but I may be wrong on this > analysis). -- 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-3426) regression : in plugin configuration doesn't override plugin classpath
regression : in plugin configuration doesn't override plugin classpath --- Key: MNG-3426 URL: http://jira.codehaus.org/browse/MNG-3426 Project: Maven 2 Issue Type: Bug Components: Plugin API Affects Versions: 2.0.8 Reporter: nicolas de loof Priority: Critical Many maven plugins are wrapper around other tools. The plugin is designed for a version of the tool, and in many case user will want to use a specific version without having to patch the plugin. The element on plugin configuration is a common way to do this, by overriding the plugin POM dependency with another version. This used to work with maven < 2.0.8 In maven 2.0.8, this doesn't work anomire as the set in plugin configuration is added to classpath, as a duplicate for the on declared by the plugin but LATER in the classpath. -- 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-3407) improve mirroring support
[
http://jira.codehaus.org/browse/MNG-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MNG-3407.
Resolution: Fixed
Fix Version/s: 2.0.9
> improve mirroring support
> -
>
> Key: MNG-3407
> URL: http://jira.codehaus.org/browse/MNG-3407
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
>Affects Versions: 2.0.8
>Reporter: nicolas de loof
>Assignee: nicolas de loof
>Priority: Trivial
> Fix For: 2.0.9
>
>
> * is a helpful way to ensure maven doesn't get artifacts from the
> Internet in a corporate environment where we want all artifacts to be managed
> & backed-up.
> Usefull but limited, as this requires the mirror repository to proxy ALL
> repositories, beeing snapshots or not.
> Using the repository ID to build the mirror URL can make things cleaner :
>
> *
> http://mymirror/archiva/repository/{0}
> central
>
> With such a configuration, users can setup dedicated managed repository for
> any public repository they want to mirror. Using archiva makes this use case
> simple.
--
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-3407) improve mirroring support
[
http://jira.codehaus.org/browse/MNG-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124144
]
nicolas de loof commented on MNG-3407:
--
Stupid typo in description, must read :
archiva
http://mymirror/archiva/repository/{0}
*
To automagically translate request to apache.snapshots to
http://mymirror/archiva/repository/apache.snapshots
> improve mirroring support
> -
>
> Key: MNG-3407
> URL: http://jira.codehaus.org/browse/MNG-3407
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
>Affects Versions: 2.0.8
>Reporter: nicolas de loof
>Assignee: nicolas de loof
>Priority: Trivial
>
> * is a helpful way to ensure maven doesn't get artifacts from the
> Internet in a corporate environment where we want all artifacts to be managed
> & backed-up.
> Usefull but limited, as this requires the mirror repository to proxy ALL
> repositories, beeing snapshots or not.
> Using the repository ID to build the mirror URL can make things cleaner :
>
> *
> http://mymirror/archiva/repository/{0}
> central
>
> With such a configuration, users can setup dedicated managed repository for
> any public repository they want to mirror. Using archiva makes this use case
> simple.
--
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-3407) improve mirroring support
improve mirroring support
-
Key: MNG-3407
URL: http://jira.codehaus.org/browse/MNG-3407
Project: Maven 2
Issue Type: Improvement
Components: Artifacts and Repositories
Affects Versions: 2.0.8
Reporter: nicolas de loof
Priority: Trivial
* is a helpful way to ensure maven doesn't get artifacts from the
Internet in a corporate environment where we want all artifacts to be managed &
backed-up.
Usefull but limited, as this requires the mirror repository to proxy ALL
repositories, beeing snapshots or not.
Using the repository ID to build the mirror URL can make things cleaner :
*
http://mymirror/archiva/repository/{0}
central
With such a configuration, users can setup dedicated managed repository for any
public repository they want to mirror. Using archiva makes this use case
simple.
--
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-3397) [RFC] change the POM to use attributes
[ http://jira.codehaus.org/browse/MNG-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123993 ] nicolas de loof commented on MNG-3397: -- I tried to enable the "flat" modello format for collections, to change : xx xx xx .. to the more convice : xx but this didn't worked : the modello generated parser still search the "executions" in XML stream. Not investigated more yet on this. > [RFC] change the POM to use attributes > -- > > Key: MNG-3397 > URL: http://jira.codehaus.org/browse/MNG-3397 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 2.0.8 >Reporter: Brett Porter > -- 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-132) dependencies with same artifactId and != groupId result is conflicts in WEB-INF/lib
[ http://jira.codehaus.org/browse/MWAR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MWAR-132. Resolution: Duplicate > dependencies with same artifactId and != groupId result is conflicts in > WEB-INF/lib > --- > > Key: MWAR-132 > URL: http://jira.codehaus.org/browse/MWAR-132 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.1-alpha-1 >Reporter: nicolas de loof >Assignee: Olivier Lamy >Priority: Minor > Fix For: 2.1 > > > as discussed on dev mailing list (groupId/artifactId mapping for Eclipse > jars) the War plugin may fail creating the webapp WEB-INF/lib if multiple > dependencies use the same artifactId, but different groupIds. > This is not the case now as many libs are created with maven1 "Id" in mind, > for example all apache commons having "commons-" as artifactId prefix. In > future, some libs may start using simplier names and rely more on maven > groupId. For such case, the war plugin MAY provide and option to add groupIds > to artifacts copied to WEB-INF/lib. -- 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: (MECLIPSE-79) exclude dependencies from the Classpath Container
[ http://jira.codehaus.org/browse/MECLIPSE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MECLIPSE-79. --- Assignee: nicolas de loof Resolution: Fixed Fix Version/s: 2.5 patch applied with minor change : groupId artifactId separator changed to ":" as this is the conventions used by other maven plugins (maven-assembly-plugin for example) : junit:junit > exclude dependencies from the Classpath Container > - > > Key: MECLIPSE-79 > URL: http://jira.codehaus.org/browse/MECLIPSE-79 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: Dependencies resolution and build path > Environment: Windows, Eclipse 3.1.2 >Reporter: Martin Goldhahn >Assignee: nicolas de loof > Fix For: 2.5 > > Attachments: MECLIPSE-79.patch > > > There are some dependencies that need to be in the POM in order to compile > the project (e.g. javax.servlet). When I use Sysdeo's Tomcat plugin, I get an > error because the servlet classes from the POM are included in the classpath > via the classpath container. -- 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: (MRM-678) 404 errors on proxies should be cached
[ http://jira.codehaus.org/browse/MRM-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MRM-678. --- Resolution: Fixed Fix Version/s: 1.1 testcase updated to fetch proxies 2 times. Depending on cacheFailure enabled / disabled, the wagonMock ensure cahce has been used or not. > 404 errors on proxies should be cached > -- > > Key: MRM-678 > URL: http://jira.codehaus.org/browse/MRM-678 > Project: Archiva > Issue Type: Improvement > Components: remote proxy >Affects Versions: 1.1 >Reporter: nicolas de loof >Assignee: nicolas de loof >Priority: Minor > Fix For: 1.1 > > > Using maven eclipse plugin with DownloadSources=true creates lot's of request > to the repository for -sources and -javadocs. Many artifacts don't have such > bundles. > When archiva is configured with multiple proxies (central + java.net + jboss > ...) a single running "mvn eclipse:eclipse" will result in many 404 request > on proxies that SHOULD be cached. The cache time-to-live (30 minute) is > sufficient to get new artifacts when they get deployed. > There is allready an UrlFailureCache but is only used to cache > ProxyExceptions. -- 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: (MRM-667) Timeout implementation for Archiva
[ http://jira.codehaus.org/browse/MRM-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MRM-667. --- Assignee: nicolas de loof Resolution: Fixed Fix Version/s: 1.1 patch applied (rev 615848) > Timeout implementation for Archiva > -- > > Key: MRM-667 > URL: http://jira.codehaus.org/browse/MRM-667 > Project: Archiva > Issue Type: Improvement >Affects Versions: 1.0.1 >Reporter: James William Dumay >Assignee: nicolas de loof > Fix For: 1.1 > > Attachments: MRM-667.patch > > > This patch replaces Wagon HTTP lightweight with Wagon HTTP to allow for > connection timeouts. > By using Wagon HTTP, we also get connection pooling for free (YAY) -- 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
