[jira] Commented: (MNG-2816) Pom without xsd import is not validated
[ http://jira.codehaus.org/browse/MNG-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87339 ] Trygve Laugstol commented on MNG-2816: -- This is a feature, not a bug! ;) Maven doesn't use the schemas to validate in any case, and in addition it allows any element as a way to be flexible so that other tools can add extenstions without breaking maven. > Pom without xsd import is not validated > --- > > Key: MNG-2816 > URL: http://jira.codehaus.org/browse/MNG-2816 > Project: Maven 2 > Issue Type: Improvement > Components: Bootstrap & Build >Affects Versions: 2.0.4 >Reporter: Kristoffer Moum > > I added a dependency to a module a couple of days ago. I did it just a tad > too quickly (copy and paste from dependency management), and forgot to > enclose with the dependency tag, i.e. I had the following structure: > > org.springframework > spring-web > > So - what happened when I did an "mvn install" the dependency was ignored > rather than producing an error message as the pom was actually valid xml. It > would be nice to have some defaulting of xsd if none was specified. -- 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-78) create eclipse projects which are m2eclipse ready
[
http://jira.codehaus.org/browse/MECLIPSE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87342
]
Martin Onis commented on MECLIPSE-78:
-
Rob,
Yes the child POMs reference back to their parent (by both
groupId/artifactId/version and by relativePath).
Point 2 is not something I have a problem with. By removing the manual
configuration of th classpath I effectively negated it's effect. I just thought
you would want to know that it's there :) The other configuration items only
showed up once, so no problem there.
The main problem I have is that the plugin sees the configured {{m2eclipse}}
flag only at the root POM level. If I add a println of the value in the plugin
where it is queried in the code, I can see its value being false for all child
POMs. This is true wether I use the mvn command from the root POM directory or
from a child POM directory. The {{downloadSources}} flag however is seen
throughout the POM tree.
This is the reason I 'patched your patch' ;-) locally, so it's hardwired to
true (the configuration item in my POM now only serves as a reminder).
I'm sure that by the time they they push this fix into the project someone will
check the code and fix the configuration issue (I'm confused myself about how
to fix that).
> create eclipse projects which are m2eclipse ready
> -
>
> Key: MECLIPSE-78
> URL: http://jira.codehaus.org/browse/MECLIPSE-78
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Environment: Fedora Core 3, Sun JDK 1.5.0.06, Eclipse 3.1.1, Maven
> 2.0.2
>Reporter: Joshua Nichols
> Attachments: m2eclipse-add-repo-tag-2.3.patch,
> m2eclipse-add-repo.patch, m2eclipse.patch, m2eclipse.patch, m2eclipse.patch,
> m2eclipse.patch, MECLIPSE-78-tag-2.3-rev2.patch, MECLIPSE-78-tag-2.3.patch,
> MECLIPSE-78.patch
>
>
> WIth the recent development of the m2eclipse plugin, I believe it is useful
> to create eclipse projects via mvn eclipse:eclipse that use m2eclipse from
> the start. One of the advantages of using m2eclipse is that you don't have to
> rerun eclipse:eclipse when you update any dependencies.
> A few things are necessary to accomplish this, in terms of changes to
> .classpath and .project.
> .project needs a new nature and builder added. For the builder:
>
> org.maven.ide.eclipse.maven2Builder
>
>
> For the nature:
> org.maven.ide.eclipse.maven2Nature
> In the .classpath, we need to add:
>path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
> In .classpath, you also don't want entries path="M2_REPO/blah/blah/x.y.z/blah-x.y.z.jar"/>, because they would conflict
> with m2eclipse setting up 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] Updated: (MJXR-19) JXR Plugin ignores the reporting output directory when generating cross reference
[ http://jira.codehaus.org/browse/MJXR-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodrigo Ruiz updated MJXR-19: - Attachment: module.zip A simple project to be used as test case. > JXR Plugin ignores the reporting output directory when generating cross > reference > - > > Key: MJXR-19 > URL: http://jira.codehaus.org/browse/MJXR-19 > Project: Maven 2.x JXR Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Eric Helfrich > Attachments: module.zip > > > The JXR Plugin ignores the reporting outputDirectory when generating the > cross reference and puts it in target/site instead -- 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: (MJXR-19) JXR Plugin ignores the reporting output directory when generating cross reference
[ http://jira.codehaus.org/browse/MJXR-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87346 ] Rodrigo Ruiz commented on MJXR-19: -- The problem becomes obvious with the following command: mvn site:stage -DstagingDirectory=... The xref is missing, and only a stylesheet and an empty index.html are generated instead. > JXR Plugin ignores the reporting output directory when generating cross > reference > - > > Key: MJXR-19 > URL: http://jira.codehaus.org/browse/MJXR-19 > Project: Maven 2.x JXR Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Eric Helfrich > Attachments: module.zip > > > The JXR Plugin ignores the reporting outputDirectory when generating the > cross reference and puts it in target/site instead -- 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-1381) Asterisk-Java 0.3-m2
Asterisk-Java 0.3-m2 Key: MAVENUPLOAD-1381 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1381 Project: maven-upload-requests Issue Type: Task Reporter: Stefan Reuter http://asterisk-java.org -- 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: (CONTINUUM-1158) Could not edit roles with latest 1.1 SNAPSHOT
Could not edit roles with latest 1.1 SNAPSHOT
-
Key: CONTINUUM-1158
URL: http://jira.codehaus.org/browse/CONTINUUM-1158
Project: Continuum
Issue Type: Bug
Components: Security
Affects Versions: 1.1
Environment: 1.1-SNAPSHOT 2007028
Reporter: Stephane Nicoll
Priority: Critical
On one of the latest snapshot, we're unable to edit the guest account (or any
other account BTW). To reproduce:
* Login as admin
* Click on users
* Click on guest
* Click on edit roles
You should receive the following message:
{noformat}
* Cannot use AssignmentsAction for RBAC Edit User with an empty principal.
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-78) create eclipse projects which are m2eclipse ready
[ http://jira.codehaus.org/browse/MECLIPSE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87355 ] Rob Baily commented on MECLIPSE-78: --- Thanks for the info Martin. I'm not sure why it is not working for you. We actually have a master project where we define the setting and that has 6 subprojects and then one of those has 2 subprojects and the setting is passed down to all of them. Everything is working fine in our case. I would try to add test cases to the patch but I am having a hard time getting the existing test cases to work due to what seem like dependency or environment problems so I haven't been able to add my own. > create eclipse projects which are m2eclipse ready > - > > Key: MECLIPSE-78 > URL: http://jira.codehaus.org/browse/MECLIPSE-78 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Environment: Fedora Core 3, Sun JDK 1.5.0.06, Eclipse 3.1.1, Maven > 2.0.2 >Reporter: Joshua Nichols > Attachments: m2eclipse-add-repo-tag-2.3.patch, > m2eclipse-add-repo.patch, m2eclipse.patch, m2eclipse.patch, m2eclipse.patch, > m2eclipse.patch, MECLIPSE-78-tag-2.3-rev2.patch, MECLIPSE-78-tag-2.3.patch, > MECLIPSE-78.patch > > > WIth the recent development of the m2eclipse plugin, I believe it is useful > to create eclipse projects via mvn eclipse:eclipse that use m2eclipse from > the start. One of the advantages of using m2eclipse is that you don't have to > rerun eclipse:eclipse when you update any dependencies. > A few things are necessary to accomplish this, in terms of changes to > .classpath and .project. > .project needs a new nature and builder added. For the builder: > > org.maven.ide.eclipse.maven2Builder > > > For the nature: > org.maven.ide.eclipse.maven2Nature > In the .classpath, we need to add: >path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/> > In .classpath, you also don't want entries path="M2_REPO/blah/blah/x.y.z/blah-x.y.z.jar"/>, because they would conflict > with m2eclipse setting up 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] Commented: (MNG-2795) Classloader problem loading a resource from a build extension Jar : difference between 2.0.4 and (future) 2.0.5
[ http://jira.codehaus.org/browse/MNG-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87364 ] Fabrice BELLINGARD commented on MNG-2795: - Well, I've just tried this test project again, with a clean installation of Maven (no local repository and the latests build of Maven 2.0.5), and when I uncomment the dependencies in the "Checkstyle-config" project's POM, then the build fails when I do the "mvn checkstyle:checkstyle" on the "TestProject" project This is so weird... I can't see anything specific to my environnement (Java 1.4.2_04). Have you tried with a clean installation as well? > Classloader problem loading a resource from a build extension Jar : > difference between 2.0.4 and (future) 2.0.5 > --- > > Key: MNG-2795 > URL: http://jira.codehaus.org/browse/MNG-2795 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.5 >Reporter: Fabrice BELLINGARD > Assigned To: Jason van Zyl > Fix For: 2.0.5 > > Attachments: Checkstyle-2.0.4.txt, Checkstyle-2.0.5.txt, > Test-BuildExtension.zip > > > I had a problem when executing the Checkstyle plugin (version 2.1) with the > pre-release of Maven 2.0.5. So I dug a bit to see if this could be related to > maven core or not, and here is what I found. > I isolated the code that breaks the build in the checkstyle plugin: it > happens when the plugin tries to load my Checkstyle configuration file, which > is actually located in a JAR that is specified in the build extensions. The > code lies in the Locator#resolveLocation() method: > // Attempt a Resource. > URL url = this.getClass().getClassLoader().getResource( > location ); > This code returns null for the "url" variable, which in turns breaks the > plugin because it doesn't find any configuration file. > I haven't had the time to dig more into it, but I found the following issue > that might be related to this problem: "MNG-2228 : Classloader problem > loading jars from build extensions". Brett and Carlos worked on it and fixed > it, so maybe they could tell more about it. > I attached the logs of the execution with Maven 2.0.4 (which works fine) and > Maven 2.0.5 (which breaks). I haven't had the time yet to dig further into > that problem. -- 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: (CONTINUUM-1158) Could not edit roles with latest 1.1 SNAPSHOT
[
http://jira.codehaus.org/browse/CONTINUUM-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87365
]
Stephane Nicoll commented on CONTINUUM-1158:
The remember me feature does not work either.
> Could not edit roles with latest 1.1 SNAPSHOT
> -
>
> Key: CONTINUUM-1158
> URL: http://jira.codehaus.org/browse/CONTINUUM-1158
> Project: Continuum
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.1
> Environment: 1.1-SNAPSHOT 2007028
>Reporter: Stephane Nicoll
>Priority: Critical
>
> On one of the latest snapshot, we're unable to edit the guest account (or any
> other account BTW). To reproduce:
> * Login as admin
> * Click on users
> * Click on guest
> * Click on edit roles
> You should receive the following message:
> {noformat}
> * Cannot use AssignmentsAction for RBAC Edit User with an empty principal.
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2817) Add identity specification in maven-model and maven-settings
[
http://jira.codehaus.org/browse/MNG-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87366
]
Vincent Siveton commented on MNG-2817:
--
Modello already generates these methods, just add the identifier parameter:
{noformat}
name
3.0.0+
String
true
{noformat}
> Add identity specification in maven-model and maven-settings
>
>
> Key: MNG-2817
> URL: http://jira.codehaus.org/browse/MNG-2817
> Project: Maven 2
> Issue Type: Bug
>Reporter: Vincent Siveton
>
> Some generated objects are used in lists. Thus, it will be very useful to
> have identity specification for them: equals(..) and hashcode() (see
> MODELLO-43)
> For instance, see org.apache.maven.model.Resource used in
> model/build/resources
--
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: (CONTINUUM-1158) Could not edit roles with latest 1.1 SNAPSHOT
[
http://jira.codehaus.org/browse/CONTINUUM-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87368
]
Wendy Smoak commented on CONTINUUM-1158:
What date is your snapshot from? 20070208 or 20070128?
The 'edit roles' feature is fixed in the plexus-security example app as of
20070211.
You might want to open a separate issue for 'remember me' or change the subject
of this one.
> Could not edit roles with latest 1.1 SNAPSHOT
> -
>
> Key: CONTINUUM-1158
> URL: http://jira.codehaus.org/browse/CONTINUUM-1158
> Project: Continuum
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.1
> Environment: 1.1-SNAPSHOT 2007028
>Reporter: Stephane Nicoll
>Priority: Critical
>
> On one of the latest snapshot, we're unable to edit the guest account (or any
> other account BTW). To reproduce:
> * Login as admin
> * Click on users
> * Click on guest
> * Click on edit roles
> You should receive the following message:
> {noformat}
> * Cannot use AssignmentsAction for RBAC Edit User with an empty principal.
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1158) Could not edit roles with latest 1.1 SNAPSHOT
[
http://jira.codehaus.org/browse/CONTINUUM-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87369
]
Stephane Nicoll commented on CONTINUUM-1158:
20070208. I'll try with the latest snapshot and update this issue accordingly.
> Could not edit roles with latest 1.1 SNAPSHOT
> -
>
> Key: CONTINUUM-1158
> URL: http://jira.codehaus.org/browse/CONTINUUM-1158
> Project: Continuum
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.1
> Environment: 1.1-SNAPSHOT 2007028
>Reporter: Stephane Nicoll
>Priority: Critical
>
> On one of the latest snapshot, we're unable to edit the guest account (or any
> other account BTW). To reproduce:
> * Login as admin
> * Click on users
> * Click on guest
> * Click on edit roles
> You should receive the following message:
> {noformat}
> * Cannot use AssignmentsAction for RBAC Edit User with an empty principal.
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRRESOURCES-7) Multiple entries are ignored
[ http://jira.codehaus.org/browse/MRRESOURCES-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp closed MRRESOURCES-7. - Resolution: Fixed Fix Version/s: 1.0-alpha-2 This is fixed on trunk. I deployed a new snapshot with this fixed last friday. You can use the 1.0-alpha-2-SNAPSHOT version from the apache snapshot repository to test it. (You're correct, this bug should have been reported in JIRA. Thanks.) Dan > Multiple entries are ignored > - > > Key: MRRESOURCES-7 > URL: http://jira.codehaus.org/browse/MRRESOURCES-7 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Al Maw > Assigned To: Daniel Kulp > Fix For: 1.0-alpha-2 > > Attachments: remote-resources-multiple-resourceBundle-issue.txt > > > Configuration is as in the attachment. > The key thing is that we're doing this: > > org.apache:apache-jar-resource-bundle:1.0 > > org.apache:apache-incubator-disclaimer-resource-bundle:1.0 > > We're finding that the first bundle is used just fine, but the second one is > not. > Expected result from the above config is that the JAR packaged for the > project should have: > META-INF/NOTICE.txt > META-INF/LICENSE.txt > META-INF/DISCLAIMER.txt > However, the last of these (from apache-incubator-disclaimer-resource-bundle) > is missing. > It may be that this has already been fixed, but I couldn't find a closed bug > for it and I'm sorry, but I haven't the time right now to build out of > subversion and try the trunk version to find out. This should be an easy one > to test, too. Even if it has been fixed in trunk, I reckon it should be noted > here in JIRA so it makes the changelog. :-) > Thanks -- Al -- 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: (MRRESOURCES-8) Should be able to pass additional properties into velocity
Should be able to pass additional properties into velocity -- Key: MRRESOURCES-8 URL: http://jira.codehaus.org/browse/MRRESOURCES-8 Project: Maven 2.x Remote Resources Plugin Issue Type: New Feature Affects Versions: 1.0-alpha-1 Reporter: Daniel Kulp Since the remote resources are velocity templates, we should be able to pass additional properties (like a build number) into velocity. -- 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: (MRRESOURCES-9) For apache-jar-resource-bundle, would be nice to optionally have license information in the NOTICE
For apache-jar-resource-bundle, would be nice to optionally have license information in the NOTICE -- Key: MRRESOURCES-9 URL: http://jira.codehaus.org/browse/MRRESOURCES-9 Project: Maven 2.x Remote Resources Plugin Issue Type: New Feature Affects Versions: 1.0-alpha-1 Reporter: Daniel Kulp The velocity template could be updated to optionally allow a "License" line for each dependent project. Kind of like: This product includes/uses software, Apache CXF Runtime Simple Frontend (http://cwiki.apache.org/confluence/display/CXF/Index), developed by Apache Software Foundation (http://www.apache.org/) License: The Apache Software License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0.txt) Would make auditing the NOTICE file a bit easier. -- 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: (MRRESOURCES-10) Generated eclipse projects complain about duplicated resources
Generated eclipse projects complain about duplicated resources -- Key: MRRESOURCES-10 URL: http://jira.codehaus.org/browse/MRRESOURCES-10 Project: Maven 2.x Remote Resources Plugin Issue Type: Bug Affects Versions: 1.0-alpha-1 Reporter: Daniel Kulp If you have the remote-resources plugin configured, but you use have a NOTICE file in your own src/main/resources directory to override the generated one, eclipse:eclipse generates a project that eclipse complains about duplicated resources. -- 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: (CONTINUUM-1158) Could not edit roles with latest 1.1 SNAPSHOT
[
http://jira.codehaus.org/browse/CONTINUUM-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87376
]
Stephane Nicoll commented on CONTINUUM-1158:
The latest snapshot of continuum still uses an older plexus-security build:
1.0-alpha-10-20070208.205557-10
Could you please deploy a new version of 1.0-alpha-10-SNAPSHOT and use it?
> Could not edit roles with latest 1.1 SNAPSHOT
> -
>
> Key: CONTINUUM-1158
> URL: http://jira.codehaus.org/browse/CONTINUUM-1158
> Project: Continuum
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.1
> Environment: 1.1-SNAPSHOT 2007028
>Reporter: Stephane Nicoll
>Priority: Critical
>
> On one of the latest snapshot, we're unable to edit the guest account (or any
> other account BTW). To reproduce:
> * Login as admin
> * Click on users
> * Click on guest
> * Click on edit roles
> You should receive the following message:
> {noformat}
> * Cannot use AssignmentsAction for RBAC Edit User with an empty principal.
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-228) CLONE -eclipse:eclipse goal should handle includes and excludes of the maven-compiler-plugin
CLONE -eclipse:eclipse goal should handle includes and excludes of the maven-compiler-plugin Key: MECLIPSE-228 URL: http://jira.codehaus.org/browse/MECLIPSE-228 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Versions: 2.0 Reporter: Diego Ballve Assigned To: fabrizio giustina Fix For: 2.3 The maven-compiler-plugin allows a configuration such as: maven-compiler-plugin **/idl/*Factory.java the generated .classpath file currently does not mention the excluded part: which should be: -- 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-228) CLONE -eclipse:eclipse goal should handle includes and excludes of the maven-compiler-plugin
[ http://jira.codehaus.org/browse/MECLIPSE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diego Ballve updated MECLIPSE-228: -- Attachment: includeExclude.patch This patch seems to solve the issue on include/exclude not being considered for java sources and tests (works for me mode, sorry, no test). Feel free to include it in svn if you find it appropriate. > CLONE -eclipse:eclipse goal should handle includes and excludes of the > maven-compiler-plugin > > > Key: MECLIPSE-228 > URL: http://jira.codehaus.org/browse/MECLIPSE-228 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Diego Ballve > Assigned To: fabrizio giustina > Fix For: 2.3 > > Attachments: includeExclude.patch > > > The maven-compiler-plugin allows a configuration such as: > > maven-compiler-plugin > > > **/idl/*Factory.java > > > > the generated .classpath file currently does not mention the excluded part: > > > which should be: >path="src/main/java"/> >path="target/generated-sources/idl"/> -- 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: (MEV-498) javax.xml.ws:jaxws-api:2.1 is bad
[ http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87378 ] Carlos Sanchez commented on MEV-498: > jaxws-maven-plugin is in an odd situation where most of its dependencies are > in java.net maven1 repo. everything in the central repo needs all dependencies in the central repo, so you have to ask for a push of what you need from the java.net repo before releasing the plugin. > One of the dependency (jaxws-api) happen to be at repo1 as well. see previous comment, all of them need to be in repo1 > Since repo1 is primary repo, its jaxws-api is picked up first and therefore > jaxws-maven-plugin is unusable. same thing, released versions have to build against repo1 and only repo1 > Tell me what is correct action for this? Have java.net to pump up its release > number which I dont think it wil be available until 2.2. as I said before: "the only thing that can be done right now is upload the good jar as version 2.1-1, state in the pom description that it's a fix of 2.1" > Question, why does repo1 have a deployment of jaxws-2.1 way before it is > official released? there was an attempt to get java.net repo synced automatically and everything was pushed to repo1. For other problems like this now is no longer automatic, but the previous stuff is already there. It's not my fault if they change released versions in their repo which is a VERY BAD thing. > javax.xml.ws:jaxws-api:2.1 is bad > - > > Key: MEV-498 > URL: http://jira.codehaus.org/browse/MEV-498 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid POM >Reporter: Dan Tran > > Sun just released jaxws 2.1 and the jaxws-api available at repo1.maven.org is > not the same with the Sun's one (both pom and the jar ) > I am working jaxws-maven-plugin and the generate code crash due to missing > interfaces > We can either sync the sun version over, or remove it from repo1 to remove > confusion > Here is the link to java.net repo > https://maven-repository.dev.java.net/nonav/repository/com.sun.xml.ws/ -- 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: (MEV-499) Latest version of clover plugin in maven.metadata.xml
Latest version of clover plugin in maven.metadata.xml - Key: MEV-499 URL: http://jira.codehaus.org/browse/MEV-499 Project: Maven Evangelism Issue Type: Bug Reporter: Anver Sotnikov Central Repository contains clover plugin version 2.3 but metadata xml defines that latest version is 2.2. http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/maven/plugins/maven-clover-plugin/maven-metadata.xml It creates a bit of inconvenience. Can you update maven-metadata.xml in order to reflect correct latest version? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1379) Please upload EZMorph-1.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1379. --- Assignee: Carlos Sanchez Resolution: Fixed > Please upload EZMorph-1.0.1 > --- > > Key: MAVENUPLOAD-1379 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1379 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andres Almiray > Assigned To: Carlos Sanchez > > EZMorph is simple java library for transforming an Object to another Object. > This release covers minor bugfixes and is needed for the next release of > Json-lib (1.0) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1381) Asterisk-Java 0.3-m2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1381. --- Assignee: Carlos Sanchez Resolution: Fixed > Asterisk-Java 0.3-m2 > > > Key: MAVENUPLOAD-1381 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1381 > Project: maven-upload-requests > Issue Type: Task >Reporter: Stefan Reuter > Assigned To: Carlos Sanchez > > http://asterisk-java.org -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1378) collections-generic upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1378. --- Assignee: Carlos Sanchez Resolution: Fixed > collections-generic upload request > -- > > Key: MAVENUPLOAD-1378 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1378 > Project: maven-upload-requests > Issue Type: Task >Reporter: tom nelson > Assigned To: Carlos Sanchez > > http://collections.sourceforge.net/maven/collections-generic-4.01-bundle.jar > http://collections.sourceforge.net > I am not a developer for this project, however I have coordinated > this request with a developer > (Matt Hall [EMAIL PROTECTED]), who placed the bundle > file in the project web-space for this request. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1380) Please sync with Json-lib repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1380. --- Assignee: Carlos Sanchez Resolution: Fixed > Please sync with Json-lib repo > -- > > Key: MAVENUPLOAD-1380 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1380 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andres Almiray > Assigned To: Carlos Sanchez > > Please sync with Json-lib's repo. The shell can be found at > http://json-lib.sourceforge.net/net.sf.json-lib.sh > The repo contains jars for binary, source and javadoc with classifiers jdk13 > and jdk15, release 1.0 > I've already subscribed to the repository@apache.org > Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1377) Please upload version 1.0.2 of the hivedoc-plugin
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1377. --- Assignee: Carlos Sanchez Resolution: Fixed > Please upload version 1.0.2 of the hivedoc-plugin > - > > Key: MAVENUPLOAD-1377 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1377 > Project: maven-upload-requests > Issue Type: Task >Reporter: Marcus Schulte > Assigned To: Carlos Sanchez > > New version of the hivedoc-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] Commented: (MAVENUPLOAD-1374) Dozer is a powerful, yet simple Java Bean to Java Bean mapper that recursively copies data from one object to another.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87382 ] Carlos Sanchez commented on MAVENUPLOAD-1374: - These dependencies are not in the repo, and seems to me that you are using different groups for Sun libraries, instead of using the ones already in the repo (javax.*) net.sf.dozer weather-forecast-schemas 1.0 test net.sf.dozer jsr173-api 1.0 test net.sf.dozer parent-child-generated-objects 1.0 test net.sf.dozer jaxb-test 1.0 test net.sf.dozer jaxb-api 1.0 test net.sf.dozer jaxb-impl 1.0 test net.sf.dozer jaxb-libs 1.0 test net.sf.dozer jaxb-xjc 1.0 test net.sf.dozer jax-qname 1.0 test net.sf.dozer namespace 1.0 test > Dozer is a powerful, yet simple Java Bean to Java Bean mapper that > recursively copies data from one object to another. > --- > > Key: MAVENUPLOAD-1374 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1374 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Tierney > Attachments: dozer-3.0-bundle.jar > > > Dozer is a powerful, yet simple Java Bean to Java Bean mapper that > recursively copies data from one object to another. Typically, these Java > Beans will be of different complex types. > Dozer supports simple property mapping, complex type mapping, bi-directional > mapping, implicit-explicit mapping, as well as recursive mapping. This > includes mapping collection attributes that also need mapping at the element > level. > Dozer not only supports mapping between attribute names, but also converting > between types. Many conversion scenarios are supported out of the box, but > Dozer also allows you to specify custom conversions via XML. > The mapper is used any time you need to take one type of Java Bean and map it > to another type of Java Bean. Most field mapping can be done automatically by > Dozer using reflection, but any custom mapping can be predescribed in XML > format. Mapping is bi-directional so only one relationship between classes > needs defining. If any property names on both objects are the same you do not > even need to do any explicit property mapping for these fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1376) Laf-Widget ant tasks
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1376. --- Assignee: Carlos Sanchez Resolution: Fixed > Laf-Widget ant tasks > > > Key: MAVENUPLOAD-1376 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1376 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tassilo Schweyer > Assigned To: Carlos Sanchez > > Laf-Plugin provides support for common "feel" widgets in look-and-feel > libraries > This package includes some useful ant tasks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1375) Laf-Widget
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1375. --- Assignee: Carlos Sanchez Resolution: Fixed > Laf-Widget > -- > > Key: MAVENUPLOAD-1375 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1375 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tassilo Schweyer > Assigned To: Carlos Sanchez > > Laf-Plugin provides support for common "feel" widgets in look-and-feel > libraries -- 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-197) Release plugin documentation on maven.apache.org has broken link to release:rollback
Release plugin documentation on maven.apache.org has broken link to release:rollback Key: MRELEASE-197 URL: http://jira.codehaus.org/browse/MRELEASE-197 Project: Maven 2.x Release Plugin Issue Type: Bug Reporter: Harold Shinsato The website lists a release:rollback goal with a broken link. http://maven.apache.org/plugins/maven-release-plugin/ Notice the link with the text "release:rollback", it links to http://maven.apache.org/plugins/maven-release-plugin/rollback-mojo.html which is a non-existant page. This goal is not listed in other pages of the documentation for this plugin, so I'm assuming it no longer exists or was deleted. Notice that this info page doesn't reference the release:rollback. http://maven.apache.org/plugins/maven-release-plugin/plugin-info.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] Reopened: (MDEP-50) dependency:unpack doesn't seem to handle version ranges
[
http://jira.codehaus.org/browse/MDEP-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox reopened MDEP-50:
---
The code changes for this are destabilizing core functionality.
> dependency:unpack doesn't seem to handle version ranges
> ---
>
> Key: MDEP-50
> URL: http://jira.codehaus.org/browse/MDEP-50
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
>Affects Versions: 1.0
> Environment: Java 1.5
>Reporter: Martin Goldhahn
> Assigned To: Brian Fox
> Fix For: 2.0-alpha-2
>
>
> When I use the dependency unpack goal and a version range as shown below,
> Maven cannot download the artifact from the repository. There is a version
> 1.4.1 in the repository. If I use the specific version number 1.4.1. It works.
>
>
> org.codehaus.mojo
> dependency-maven-plugin
>
>
> unpack
> compile
>
> unpack
>
>
>
>
> my.package
> concept
> [1.4,1.5)
> res
>
> ${project.build.sourceDirectory}/../webapp/res
>
>
>
>
>
>
--
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: (MRRESOURCES-8) Should be able to pass additional properties into velocity
[ http://jira.codehaus.org/browse/MRRESOURCES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated MRRESOURCES-8: -- Description: Since the remote resources are velocity templates, we should be able to pass additional properties (like a build number) into velocity. was: Since the remote resources are velocity templates, we should be able to pass additional properties (like a build number) into velocity. Fix Version/s: 1.0-alpha-2 > Should be able to pass additional properties into velocity > -- > > Key: MRRESOURCES-8 > URL: http://jira.codehaus.org/browse/MRRESOURCES-8 > Project: Maven 2.x Remote Resources Plugin > Issue Type: New Feature >Affects Versions: 1.0-alpha-1 >Reporter: Daniel Kulp > Assigned To: Daniel Kulp > Fix For: 1.0-alpha-2 > > > Since the remote resources are velocity templates, we should be able to pass > additional properties (like a build number) into velocity. -- 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: (MRRESOURCES-10) Generated eclipse projects complain about duplicated resources
[ http://jira.codehaus.org/browse/MRRESOURCES-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated MRRESOURCES-10: --- Description: If you have the remote-resources plugin configured, but you use have a NOTICE file in your own src/main/resources directory to override the generated one, eclipse:eclipse generates a project that eclipse complains about duplicated resources. was: If you have the remote-resources plugin configured, but you use have a NOTICE file in your own src/main/resources directory to override the generated one, eclipse:eclipse generates a project that eclipse complains about duplicated resources. Fix Version/s: 1.0-alpha-2 > Generated eclipse projects complain about duplicated resources > -- > > Key: MRRESOURCES-10 > URL: http://jira.codehaus.org/browse/MRRESOURCES-10 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Daniel Kulp > Assigned To: Daniel Kulp > Fix For: 1.0-alpha-2 > > > If you have the remote-resources plugin configured, but you use have a NOTICE > file in your own src/main/resources directory to override the generated one, > eclipse:eclipse generates a project that eclipse complains about duplicated > resources. -- 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: (MRRESOURCES-9) For apache-jar-resource-bundle, would be nice to optionally have license information in the NOTICE
[ http://jira.codehaus.org/browse/MRRESOURCES-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated MRRESOURCES-9: -- Description: The velocity template could be updated to optionally allow a "License" line for each dependent project. Kind of like: This product includes/uses software, Apache CXF Runtime Simple Frontend (http://cwiki.apache.org/confluence/display/CXF/Index), developed by Apache Software Foundation (http://www.apache.org/) License: The Apache Software License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0.txt) Would make auditing the NOTICE file a bit easier. was: The velocity template could be updated to optionally allow a "License" line for each dependent project. Kind of like: This product includes/uses software, Apache CXF Runtime Simple Frontend (http://cwiki.apache.org/confluence/display/CXF/Index), developed by Apache Software Foundation (http://www.apache.org/) License: The Apache Software License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0.txt) Would make auditing the NOTICE file a bit easier. Fix Version/s: 1.0-alpha-2 > For apache-jar-resource-bundle, would be nice to optionally have license > information in the NOTICE > -- > > Key: MRRESOURCES-9 > URL: http://jira.codehaus.org/browse/MRRESOURCES-9 > Project: Maven 2.x Remote Resources Plugin > Issue Type: New Feature >Affects Versions: 1.0-alpha-1 >Reporter: Daniel Kulp > Assigned To: Daniel Kulp > Fix For: 1.0-alpha-2 > > > The velocity template could be updated to optionally allow a "License" line > for each dependent project. Kind of like: > This product includes/uses software, Apache CXF Runtime Simple Frontend > (http://cwiki.apache.org/confluence/display/CXF/Index), > developed by Apache Software Foundation (http://www.apache.org/) > License: The Apache Software License, Version 2.0 > (http://www.apache.org/licenses/LICENSE-2.0.txt) > Would make auditing the NOTICE file a bit easier. -- 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: (MRRESOURCES-1) Index for resourceBundle error messages is wrong
[ http://jira.codehaus.org/browse/MRRESOURCES-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated MRRESOURCES-1: -- Description: If I use multiple resource bundles in my config and the second one is "wrong", like: org.apache:apache-jar-resource-bundle:1.0 apache-incubator-disclaimer-resource-bundle:1.0 I get the error message: The 1st resource bundle configured must specify a groupId, artifactId, and version for a remote resource bundle. Must be of the form groupId:artifactId:version It's really the second one that's the problem. Not the first. was: If I use multiple resource bundles in my config and the second one is "wrong", like: org.apache:apache-jar-resource-bundle:1.0 apache-incubator-disclaimer-resource-bundle:1.0 I get the error message: The 1st resource bundle configured must specify a groupId, artifactId, and version for a remote resource bundle. Must be of the form groupId:artifactId:version It's really the second one that's the problem. Not the first. Fix Version/s: 1.0-alpha-2 > Index for resourceBundle error messages is wrong > > > Key: MRRESOURCES-1 > URL: http://jira.codehaus.org/browse/MRRESOURCES-1 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Bug >Reporter: Daniel Kulp > Assigned To: Jason van Zyl >Priority: Minor > Fix For: 1.0-alpha-2 > > > If I use multiple resource bundles in my config and the second one is > "wrong", like: > > org.apache:apache-jar-resource-bundle:1.0 > > apache-incubator-disclaimer-resource-bundle:1.0 > I get the error message: > The 1st resource bundle configured must specify a groupId, artifactId, and > version for a remote resource bundle. Must be of the form > groupId:artifactId:version > It's really the second one that's the problem. Not the first. -- 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: (CONTINUUM-1159) User roles are not updated when a user logs out and logs back in
User roles are not updated when a user logs out and logs back in Key: CONTINUUM-1159 URL: http://jira.codehaus.org/browse/CONTINUUM-1159 Project: Continuum Issue Type: Bug Components: Security Affects Versions: 1.1 Environment: Continuum 1.1-SNAPSHOT r506485 Reporter: Wendy Smoak When two instances of continuum are sharing one external user database, changes to user roles in one instance are not visible in the other, even after the user logs out and back in. >From #plexus confirmed, my newly granted roles do not show up, and logging out and back in doesn't help what's the timeout on the items in the cache? 600 seconds ... how about "logging out and back in should re-load a users's data" ? I had thought on login it did that, if it doesn't bug it -- 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-2676) maven-dependency-analyser shared component & plugin
[ http://jira.codehaus.org/browse/MNG-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87409 ] Joakim Erdfelt commented on MNG-2676: - Work is being done on this. * Correcting spelling everywhere. ** Analyser -> Analyzer ** Analyse -> Analyser ** Analysis ** Analyst * Using maven-shared-jar for class analysis instead of internal ASM implementation. * Correcting various JDK 1.5 usages Keep an eye out for the following subversion locations ... * https://svn.apache.org/repos/asf/maven/sandbox/shared/maven-dependency-analyzer * https://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-dependency-analyzer-plugin > maven-dependency-analyser shared component & plugin > --- > > Key: MNG-2676 > URL: http://jira.codehaus.org/browse/MNG-2676 > Project: Maven 2 > Issue Type: New Feature > Components: Dependencies >Affects Versions: 2.0.4 >Reporter: Mark Hobson > Assigned To: Joakim Erdfelt > Attachments: maven-dependency-analyser-plugin.zip, > maven-dependency-analyser.zip > > > A shared component and plugin to analyse project dependencies as described in > the thread: > http://www.mail-archive.com/dev@maven.apache.org/msg61432.html > Javadoc and tests to come when I get some more free time ;) -- 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: (NMAVEN-1) Failed to build plugins wtih csc 1.1.4322 (Microsoft)
[ http://jira.codehaus.org/browse/NMAVEN-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87410 ] Shane Isbell commented on NMAVEN-1: --- Thanks for the patch Alex! I applied it in the BUG_NMAVEN_1 branch, tested it and have merged to the trunk. In addition to the patch, I had to change some of the NUnit tests since they were also .NET 2.0 dependent. > Failed to build plugins wtih csc 1.1.4322 (Microsoft) > - > > Key: NMAVEN-1 > URL: http://jira.codehaus.org/browse/NMAVEN-1 > Project: NMaven > Issue Type: Bug > Environment: Microsoft .NET Framework 1.1.4322 >Reporter: Shane Isbell >Priority: Minor > Attachments: nmaven1Patch20070210.patch > > > This issue was submitted by Christophe Lallement on sf.net: > -- > i have this error when building nmaven-utility-settings > i suppose it's because this sources is 2.0 compatible ? > [INFO] task-segment: [install] > [INFO] > > [INFO] [compile:initialize] > [INFO] [resolver:resolve] > [INFO] [settings:generate-settings] > [INFO] [compile:generate-assembly-info] > [INFO] NMAVEN-902-000: Generating Assembly Info: Language = C_SHARP > [INFO] [compile:process-sources] > [INFO] NMAVEN-904-002: Copying source files: From = > C:\HOMEWARE\csharp\nmaven-plugins-0.13\scripts\..\nmaven-utility-settings\src\ > main\csharp, To = > C:\HOMEWARE\csharp\nmaven-plugins-0.13\scripts\..\nmaven-utility-settings\target\build-sources > [INFO] [compile:process-test-sources] > [INFO] NMAVEN-905-002: Copying test source files: From = > C:\HOMEWARE\csharp\nmaven-plugins-0.13\scripts\..\nmaven-utility-settings > \src\test\csharp, To = > C:\HOMEWARE\csharp\nmaven-plugins-0.13\scripts\..\nmaven-utility-settings\target\build-test-sources > [INFO] [resgen:copy-resources] > [INFO] [resgen:generate] > [INFO] [compile:compile] > [INFO] NMAVEN-066-012: Found Vendor = Vendor = MICROSOFT, Vendor Version = > 1.1.4322, Framework Version = 1.1.4322, Executable Path > = > [INFO] NMAVEN-068-003: Compiling Artifact: Vendor = MICROSOFT, Language = > MICROSOFT, Assembly Name = C:\HOMEWARE\csharp\nmaven-plu > gins-0.13\scripts\..\nmaven-utility-settings\target\SettingsGenerator.exe > c:\HOMEWARE\csharp\nmaven-plugins-0.13\nmaven-utility-settings\target\build-sources\nmavenSettings.cs(24,8): > error CS1518: Expecte > d class, delegate, enum, interface, or struct > c:\HOMEWARE\csharp\nmaven-plugins-0.13\nmaven-utility-settings\target\build-sources\nmavenSettings.cs(85,8): > error CS1518: Expecte > d class, delegate, enum, interface, or struct > c:\HOMEWARE\csharp\nmaven-plugins-0.13\nmaven-utility-settings\target\build-sources\nmavenSettings.cs(132,8): > error CS1518: Expect > ed class, delegate, enum, interface, or struct > c:\HOMEWARE\csharp\nmaven-plugins-0.13\nmaven-utility-settings\target\build-sources\nmavenSettings.cs(193,8): > error CS1518: Expect > ed class, delegate, enum, interface, or struct > c:\HOMEWARE\csharp\nmaven-plugins-0.13\nmaven-utility-settings\target\build-sources\nmavenSettings.cs(228,8): > error CS1518: Expect > ed class, delegate, enum, interface, or struct > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] NMAVEN-900-004: Unable to Compile: Language = C_SHARP, Vendor = null, > ArtifactType = exe, Source Directory = C:\HOMEWARE\cs > harp\nmaven-plugins-0.13\scripts\..\nmaven-utility-settings\src\main\csharp > Embedded error: NMAVEN-040-001: Could not execute: Command = csc > /out:C:\HOMEWARE\csharp\nmaven-plugins-0.13\scripts\..\nmaven-uti > lity-settings\target\SettingsGenerator.exe /target:exe > /recurse:C:\HOMEWARE\csharp\nmaven-plugins-0.13\scripts\..\nmaven-utility-s > ettings\target\build-sources\** > /reference:C:\HOMEWARE\maven-2_local\org\nunit\nunit.framework\2.2.8.0\nunit.framework.dll > /nologo > /warnaserror-, Result = 1 > [INFO] > -- 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: (NMAVEN-1) Failed to build plugins wtih csc 1.1.4322 (Microsoft)
[ http://jira.codehaus.org/browse/NMAVEN-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-1. - Resolution: Fixed Tested and merged into trunk. > Failed to build plugins wtih csc 1.1.4322 (Microsoft) > - > > Key: NMAVEN-1 > URL: http://jira.codehaus.org/browse/NMAVEN-1 > Project: NMaven > Issue Type: Bug > Environment: Microsoft .NET Framework 1.1.4322 >Reporter: Shane Isbell >Priority: Minor > Attachments: nmaven1Patch20070210.patch > > > This issue was submitted by Christophe Lallement on sf.net: > -- > i have this error when building nmaven-utility-settings > i suppose it's because this sources is 2.0 compatible ? > [INFO] task-segment: [install] > [INFO] > > [INFO] [compile:initialize] > [INFO] [resolver:resolve] > [INFO] [settings:generate-settings] > [INFO] [compile:generate-assembly-info] > [INFO] NMAVEN-902-000: Generating Assembly Info: Language = C_SHARP > [INFO] [compile:process-sources] > [INFO] NMAVEN-904-002: Copying source files: From = > C:\HOMEWARE\csharp\nmaven-plugins-0.13\scripts\..\nmaven-utility-settings\src\ > main\csharp, To = > C:\HOMEWARE\csharp\nmaven-plugins-0.13\scripts\..\nmaven-utility-settings\target\build-sources > [INFO] [compile:process-test-sources] > [INFO] NMAVEN-905-002: Copying test source files: From = > C:\HOMEWARE\csharp\nmaven-plugins-0.13\scripts\..\nmaven-utility-settings > \src\test\csharp, To = > C:\HOMEWARE\csharp\nmaven-plugins-0.13\scripts\..\nmaven-utility-settings\target\build-test-sources > [INFO] [resgen:copy-resources] > [INFO] [resgen:generate] > [INFO] [compile:compile] > [INFO] NMAVEN-066-012: Found Vendor = Vendor = MICROSOFT, Vendor Version = > 1.1.4322, Framework Version = 1.1.4322, Executable Path > = > [INFO] NMAVEN-068-003: Compiling Artifact: Vendor = MICROSOFT, Language = > MICROSOFT, Assembly Name = C:\HOMEWARE\csharp\nmaven-plu > gins-0.13\scripts\..\nmaven-utility-settings\target\SettingsGenerator.exe > c:\HOMEWARE\csharp\nmaven-plugins-0.13\nmaven-utility-settings\target\build-sources\nmavenSettings.cs(24,8): > error CS1518: Expecte > d class, delegate, enum, interface, or struct > c:\HOMEWARE\csharp\nmaven-plugins-0.13\nmaven-utility-settings\target\build-sources\nmavenSettings.cs(85,8): > error CS1518: Expecte > d class, delegate, enum, interface, or struct > c:\HOMEWARE\csharp\nmaven-plugins-0.13\nmaven-utility-settings\target\build-sources\nmavenSettings.cs(132,8): > error CS1518: Expect > ed class, delegate, enum, interface, or struct > c:\HOMEWARE\csharp\nmaven-plugins-0.13\nmaven-utility-settings\target\build-sources\nmavenSettings.cs(193,8): > error CS1518: Expect > ed class, delegate, enum, interface, or struct > c:\HOMEWARE\csharp\nmaven-plugins-0.13\nmaven-utility-settings\target\build-sources\nmavenSettings.cs(228,8): > error CS1518: Expect > ed class, delegate, enum, interface, or struct > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] NMAVEN-900-004: Unable to Compile: Language = C_SHARP, Vendor = null, > ArtifactType = exe, Source Directory = C:\HOMEWARE\cs > harp\nmaven-plugins-0.13\scripts\..\nmaven-utility-settings\src\main\csharp > Embedded error: NMAVEN-040-001: Could not execute: Command = csc > /out:C:\HOMEWARE\csharp\nmaven-plugins-0.13\scripts\..\nmaven-uti > lity-settings\target\SettingsGenerator.exe /target:exe > /recurse:C:\HOMEWARE\csharp\nmaven-plugins-0.13\scripts\..\nmaven-utility-s > ettings\target\build-sources\** > /reference:C:\HOMEWARE\maven-2_local\org\nunit\nunit.framework\2.2.8.0\nunit.framework.dll > /nologo > /warnaserror-, Result = 1 > [INFO] > -- 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-63) allow version to be stripped from useSubfolderPerArtifact
allow version to be stripped from useSubfolderPerArtifact - Key: MDEP-63 URL: http://jira.codehaus.org/browse/MDEP-63 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Reporter: Brian Fox Assigned To: Brian Fox if useSubfolderPerArtifact is used, there is no way to remove the version from the path -- 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: (MDEP-63) allow version to be stripped from useSubfolderPerArtifact
[ http://jira.codehaus.org/browse/MDEP-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MDEP-63. - Resolution: Fixed Fix Version/s: 2.0-alpha-2 The folder name logic has been rewritten to allow removing the version. Instead of using artifact.getId() as the base for the folder name, the new format is used: artifactId-classifier-[version]-type if classifier and type are the same (as in sources) and version is removed, then type is dropped. This prevents names like foo-sources-sources. (foo-sources-1.1-sources is allowed) > allow version to be stripped from useSubfolderPerArtifact > - > > Key: MDEP-63 > URL: http://jira.codehaus.org/browse/MDEP-63 > Project: Maven 2.x Dependency Plugin > Issue Type: Improvement >Reporter: Brian Fox > Assigned To: Brian Fox > Fix For: 2.0-alpha-2 > > > if useSubfolderPerArtifact is used, there is no way to remove the version > from the path -- 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-2676) maven-dependency-analyser shared component & plugin
[ http://jira.codehaus.org/browse/MNG-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MNG-2676. --- Resolution: Fixed Committed to revision 506835. > maven-dependency-analyser shared component & plugin > --- > > Key: MNG-2676 > URL: http://jira.codehaus.org/browse/MNG-2676 > Project: Maven 2 > Issue Type: New Feature > Components: Dependencies >Affects Versions: 2.0.4 >Reporter: Mark Hobson > Assigned To: Joakim Erdfelt > Attachments: maven-dependency-analyser-plugin.zip, > maven-dependency-analyser.zip > > > A shared component and plugin to analyse project dependencies as described in > the thread: > http://www.mail-archive.com/dev@maven.apache.org/msg61432.html > Javadoc and tests to come when I get some more free time ;) -- 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: (CONTINUUM-1160) Unable to add additional projects to a group (as project administrator)
Unable to add additional projects to a group (as project administrator) --- Key: CONTINUUM-1160 URL: http://jira.codehaus.org/browse/CONTINUUM-1160 Project: Continuum Issue Type: Bug Affects Versions: 1.1 Environment: Continuum 1.1-SNAPSHOT r506781 Reporter: Wendy Smoak Attachments: continuum-r506781-wrapper.log I am unable to add more projects to an existing group for which I am a Project Administrator. (Shouldn't this be called Group Administrator?) 1. Create admin user, log in as admin 2. Add m2 project: http://svn.apache.org/repos/asf/tiles/framework/trunk/pom.xml 2a. (this creates the Tiles 2 group, org.apache.tiles) 3. Create user1 account 4. Assign 'Project Administrator - Tiles 2' role to user1 5. log out as admin 6. log in as user1 7. Visit the Tiles 2 project summary page 8. Project Group Actions -> Add M2 Project -> Add 9. Attempt to add http://svn.apache.org/repos/asf/tiles/examples/trunk/tiles-showcase/pom.xml Result: blank page Log file from steps 7-9 above is attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1161) Project Administrator role is not available for Default Project Group
Project Administrator role is not available for Default Project Group - Key: CONTINUUM-1161 URL: http://jira.codehaus.org/browse/CONTINUUM-1161 Project: Continuum Issue Type: Bug Components: Web - Security Affects Versions: 1.1 Environment: Continuum 1.1-SNAPSHOT r506781 Reporter: Wendy Smoak Priority: Minor When assigning roles to users, there is no option for 'Project Administrator - Default Project Group' -- 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: (CONTINUUM-1162) Default Project Group does not appear on Project Groups page until you add projects to it
Default Project Group does not appear on Project Groups page until you add projects to it - Key: CONTINUUM-1162 URL: http://jira.codehaus.org/browse/CONTINUUM-1162 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: Continuum 1.1-SNAPSHOT r506781 Reporter: Wendy Smoak The Default Project Group does not appear on the Project Groups (groupSummary.action) page when Continuum is first installed. If you add projects to the Default Project Group, then it does appear. It should always be displayed (if the user has permission to see it.) (These tests were done while logged in as admin.) For comparison, newly added project groups containing no projects do appear in the list. -- 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
