[jira] Closed: (MNG-2819) Prevent extension scanner from looping infinitely when projects are in a flattened structure
[ http://jira.codehaus.org/browse/MNG-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2819. -- Resolution: Fixed > Prevent extension scanner from looping infinitely when projects are in a > flattened structure > > > Key: MNG-2819 > URL: http://jira.codehaus.org/browse/MNG-2819 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1.x >Reporter: Jason van Zyl > Assigned To: Jason van Zyl > > When you have a directory structure like this: > MNGECLIPSE-256pom/ > pom.xml > MNGECLIPSE-256utility/ > pom.xml > MNGECLIPSE-256web/ > pom.xml > Where the parent POM does something like: > > ../MNGECLIPSE-256web > ../MNGECLIPSE-256utility > > The extension scanner loops infinitely. Found while testing the Eclipse > Integration where it is common for users to put projects in a flattened > structure as only later versions of eclipse understand a nested structure. -- 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-2819) Prevent extension scanner from looping infinitely when projects are in a flattened structure
Prevent extension scanner from looping infinitely when projects are in a flattened structure Key: MNG-2819 URL: http://jira.codehaus.org/browse/MNG-2819 Project: Maven 2 Issue Type: Bug Affects Versions: 2.1.x Reporter: Jason van Zyl When you have a directory structure like this: MNGECLIPSE-256pom/ pom.xml MNGECLIPSE-256utility/ pom.xml MNGECLIPSE-256web/ pom.xml Where the parent POM does something like: ../MNGECLIPSE-256web ../MNGECLIPSE-256utility The extension scanner loops infinitely. Found while testing the Eclipse Integration where it is common for users to put projects in a flattened structure as only later versions of eclipse understand a nested structure. -- 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-227) mvn eclipse:eclipse for pom should create a .project file
mvn eclipse:eclipse for pom should create a .project file Key: MECLIPSE-227 URL: http://jira.codehaus.org/browse/MECLIPSE-227 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Environment: all Reporter: THURNER rupert mvn eclipse:eclipse for pom should create a .project file. currently it does nothing. this is especially annoying if using parent poms with other poms in subdirectories, see also description on http://maven.apache.org/guides/mini/guide-ide-eclipse.html. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-210) version 0.9 cannot run under eclipse 3.2.1 and 3.2 and 3.1 and Together 2006 R2!!!
[ http://jira.codehaus.org/browse/MECLIPSE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87257 ] Steinar Bang commented on MECLIPSE-210: --- This bug report is for m2eclipse, the eclipse maven plugin http://m2eclipse.codehaus.org/ and not for the maven eclipse plugin maven-eclipse-plugin http://maven.apache.org/plugins/maven-eclipse-plugin/, which is the project this is a buglist for. > version 0.9 cannot run under eclipse 3.2.1 and 3.2 and 3.1 and Together 2006 > R2!!! > -- > > Key: MECLIPSE-210 > URL: http://jira.codehaus.org/browse/MECLIPSE-210 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: PDE support > Environment: Borland Together 2006 Release 2 > Eclipse 3.1 > MyEclipse 5.1 GA >Reporter: Edward >Priority: Blocker > Attachments: error1.JPG, error2.JPG > > > I have installed M2Eclipse plugin version 0.9 by update site. > But when I navigated to Maven2 item in Preferences window, it show an error > window (error1.jpg). > As well, when selected the "Maven | Enable" in popup context menu, got "The > chosen operation is not currently avaiable." > I have tried with Eclipse 3.1, MyEclipse 5.1 and borland Together 2006 R2. > But the same result. > What a shame you guys. Please put your attention on Quality!!! -- 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: (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 ] Alex updated NMAVEN-1: -- Attachment: nmaven1Patch20070210.patch This is my first patch submission, so be gentle if I've inadvertently violated patch submission etiquette. It appears that the 1.1 compiler was unable to process the nmavenSettings.cs file because it contains partial classes. To remove the partial classes, I regenerated nmavenSettings.cs with the xsd.exe utility associated with the 1.1 SDK. The only other change I made was replacing the Single.TryParse method with a Single.Parse method in SettingsGenerator.cs because the TryParse is not 1.1 compatible. I ran the bootstrap-build.bat file successfully with both the 1.1 compiler and the 2.0 compiler. Alex > 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: (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:all-tabpanel ] Jason van Zyl closed MNG-2795. -- Resolution: Fixed Used test project and everything works fine. > 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] Updated: (MINVOKER-2) Failures are incorrectly counted
[ http://jira.codehaus.org/browse/MINVOKER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Pik updated MINVOKER-2: -- Attachment: invoker.diff diff for InvokerMojo.java > Failures are incorrectly counted > > > Key: MINVOKER-2 > URL: http://jira.codehaus.org/browse/MINVOKER-2 > Project: Maven 2.x Invoker Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Tomasz Pik > Assigned To: John Casey >Priority: Minor > Attachments: invoker.diff > > > When build hook scripts returns false projects are counted two times as > failures - first time at script execution methods and second time in runBuild > methods. > This leads to results like this: > --- > Execution Summary: > Builds Passing: -1 > Builds Failing: 2 > --- > The following builds failed: > * test1\pom.xml > * test1\pom.xml -- 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: (MINVOKER-2) Failures are incorrectly counted
Failures are incorrectly counted Key: MINVOKER-2 URL: http://jira.codehaus.org/browse/MINVOKER-2 Project: Maven 2.x Invoker Plugin Issue Type: Bug Affects Versions: 1.0 Reporter: Tomasz Pik Assigned To: John Casey Priority: Minor Attachments: invoker.diff When build hook scripts returns false projects are counted two times as failures - first time at script execution methods and second time in runBuild methods. This leads to results like this: --- Execution Summary: Builds Passing: -1 Builds Failing: 2 --- The following builds failed: * test1\pom.xml * test1\pom.xml -- 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-1377) Please upload version 1.0.2 of the hivedoc-plugin
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 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] Created: (MAVENUPLOAD-1378) collections-generic upload request
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 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] 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_87278 ] Dan Tran commented on MEV-498: -- Can you remove it from repo1? > 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: (MAVENUPLOAD-1379) Please upload EZMorph-1.0.1
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 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] Updated: (MRM-277) Proxied repositories change order when edited
[ http://jira.codehaus.org/browse/MRM-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated MRM-277: Affects Version/s: 1.0 Environment: 1.0-SNAPSHOT, r505337 > Proxied repositories change order when edited > - > > Key: MRM-277 > URL: http://jira.codehaus.org/browse/MRM-277 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0 > Environment: 1.0-SNAPSHOT, r505337 >Reporter: Wendy Smoak >Priority: Minor > > If you edit a proxied repository (to check/uncheck 'Use HTTP Proxy' for > example) the order of the list changes after you update. > To reproduce, set up more than one proxied repository, then: > 1. Administration -> Proxied Repositories > 2. Observe the order of the list of proxied repositories > 3. Edit Repository -> (make a change) -> Update Repository > 4. Compare the order of the list to (2) > They should always be in the same order. -- 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: (MRM-277) Proxied repositories change order when edited
Proxied repositories change order when edited - Key: MRM-277 URL: http://jira.codehaus.org/browse/MRM-277 Project: Archiva Issue Type: Bug Components: web application Reporter: Wendy Smoak Priority: Minor If you edit a proxied repository (to check/uncheck 'Use HTTP Proxy' for example) the order of the list changes after you update. To reproduce, set up more than one proxied repository, then: 1. Administration -> Proxied Repositories 2. Observe the order of the list of proxied repositories 3. Edit Repository -> (make a change) -> Update Repository 4. Compare the order of the list to (2) They should always be in the same order. -- 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: (MRM-278) Unable to un-check checkboxes
[ http://jira.codehaus.org/browse/MRM-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated MRM-278: Affects Version/s: 1.0 I should also admit to building it with tests skipped due to test errors in archiva-configuration. > Unable to un-check checkboxes > - > > Key: MRM-278 > URL: http://jira.codehaus.org/browse/MRM-278 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0 > Environment: 1.0-SNAPSHOT, r505337, using 'mvn jetty:run' in > archiva-webapp >Reporter: Wendy Smoak > > When editing repositories, I am unable to un-check any of the checkboxes, > such as 'Include Snapshots' or 'Use HTTP Proxy'. > The only way I can make changes is to edit ~/.m2/archiva.xml and re-start. -- 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: (SUREFIRE-101) Plugin not longer sets system properties when forking is on and debugging information is not correct
[
http://jira.codehaus.org/browse/SUREFIRE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Massol closed SUREFIRE-101.
---
Resolution: Fixed
Closing as this seems to be fixed now.
> Plugin not longer sets system properties when forking is on and debugging
> information is not correct
>
>
> Key: SUREFIRE-101
> URL: http://jira.codehaus.org/browse/SUREFIRE-101
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.0 (2.2 plugin)
>Reporter: Vincent Massol
> Assigned To: Vincent Massol
>Priority: Blocker
> Fix For: 2.3
>
> Attachments: MSUREFIRE-145.zip
>
>
> The following code is in SurefirePlugin.java:
> {code:java}
> processSystemProperties( !fork.isForking() );
> if ( getLog().isDebugEnabled() )
> {
> showMap( systemProperties, "system property" );
> }
> {code}
> 2 problems:
> 1) fork.isForking() is false when forking is enabled and thus system
> properties are not set:
> {code:java}
> protected void processSystemProperties( boolean setInSystem )
> {
> [...]
> if ( setInSystem )
> {
> // Add all system properties configured by the user
> Iterator iter = systemProperties.keySet().iterator();
> while ( iter.hasNext() )
> {
> String key = (String) iter.next();
> String value = systemProperties.getProperty( key );
> System.setProperty( key, value );
> }
> }
> }
> {code}
> 2) showMap() is called regardless of whether the system properties are set
> or not, leading to the following kind of misleading logs:
> {noformat}
> [...]
> [DEBUG] Setting system property [cargo.jetty4x.port]=[8280]
> [DEBUG] Setting system property [cargo.jetty6x.port]=[8280]
> [DEBUG] Setting system property [cargo.jetty5x.port]=[8280]
> [...]
> {noformat}
> Those properties are actually NOT set.
--
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: (MRM-278) Unable to un-check checkboxes
Unable to un-check checkboxes - Key: MRM-278 URL: http://jira.codehaus.org/browse/MRM-278 Project: Archiva Issue Type: Bug Components: web application Environment: 1.0-SNAPSHOT, r505337, using 'mvn jetty:run' in archiva-webapp Reporter: Wendy Smoak When editing repositories, I am unable to un-check any of the checkboxes, such as 'Include Snapshots' or 'Use HTTP Proxy'. The only way I can make changes is to edit ~/.m2/archiva.xml and re-start. -- 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-7) Multiple entries are ignored
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 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] Closed: (MJAR-10) dealing with licenses
[ http://jira.codehaus.org/browse/MJAR-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MJAR-10. - Resolution: Fixed This is now dealt with by the remote resources plugin. > dealing with licenses > - > > Key: MJAR-10 > URL: http://jira.codehaus.org/browse/MJAR-10 > Project: Maven 2.x Jar Plugin > Issue Type: New Feature >Reporter: Jorg Heymans >Priority: Minor > > maven could offer a configurable way to include project licenses in the jar, > briefly discussed on IRC today > jorgdoes m2 have anything built-in to deal with library licenses ? > just wondering ... > kenney tag in the pom is all I think > jorgah yep, i knew I saw something about it somewhere, tnx kenney > kenney and just distribute poms for non-freely-distributable jars > (like the sun ones), stating where you can download/purchase them > jorgmmm "Typically the licenses listed for the project are that of > the project itself, and not of dependencies." > jorgok so unless all our dependencies are good maven citizens this > won't really work ... > jorgno prob, we'll just include them ourselves then > kenney do you have to? > kenney if people distribute a jar/pom without a license, it's their > fault > jorgwell we (cocoon) have always done so > jorgthat's true though , it's up to them to include them > trygvis I think people are a bit slack when it comes to adding that > information > jorgdefinitely > kenney what about the bundle upload system? > jorgthat's why i was hoping for maven to be able enforce something > trygvis we should probably start to enumerate the various licenses and > give them IDs instead > kenney bundles have to have a LICENSE file.. where does that go? > trygvis not sure, ask carlos > kenney yeah or maybe extend the license tag to name the license > (ASL-2.0) and the online-url, or alternatively list the license content > itself.. or just add a bla-X-LICENSE.txt on ibiblio per project > jorgsomething like that yeah, and perhaps offering a configurable > way of having the license file included in the jar ? > jorgor is that a hairy legal thing maven shouldn't get into ? > trygvis kenney: the name there (ASL-2.0) would be the id > trygvis jorg: good idea > jorgit would certainly advocate , albeit rather enforced, correct > usage of 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: (MNG-2820) Deployment is stripping out the license header from the POM
Deployment is stripping out the license header from the POM --- Key: MNG-2820 URL: http://jira.codehaus.org/browse/MNG-2820 Project: Maven 2 Issue Type: Bug Components: Deployment Affects Versions: 2.0.4 Reporter: Jason van Zyl Fix For: 2.0.5 -- 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-2820) Deployment is stripping out the license header from the POM
[ http://jira.codehaus.org/browse/MNG-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2820. -- Resolution: Fixed Fixed on trunk and 2.0.x. > Deployment is stripping out the license header from the POM > --- > > Key: MNG-2820 > URL: http://jira.codehaus.org/browse/MNG-2820 > Project: Maven 2 > Issue Type: Bug > Components: Deployment >Affects Versions: 2.0.4 >Reporter: Jason van Zyl > Assigned To: Jason van Zyl > Fix For: 2.0.5 > > -- 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-2820) Deployment is stripping out the license header from the POM
[ http://jira.codehaus.org/browse/MNG-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2820: --- Fix Version/s: 2.0.5 > Deployment is stripping out the license header from the POM > --- > > Key: MNG-2820 > URL: http://jira.codehaus.org/browse/MNG-2820 > Project: Maven 2 > Issue Type: Bug > Components: Deployment >Affects Versions: 2.0.4 >Reporter: Jason van Zyl > Assigned To: Jason van Zyl > Fix For: 2.0.5 > > -- 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-181) maven2-dbunit-plugin does not work
maven2-dbunit-plugin does not work
--
Key: MASSEMBLY-181
URL: http://jira.codehaus.org/browse/MASSEMBLY-181
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Environment: maven2, dbunit2.2, mysql, netbeans, ant
Reporter: nilo de roock
Priority: Critical
In my environment this works fine in Ant.
The following pom.xml works but does nothing in mysql ( first relevant snippet,
complete pom after that ):
SNIPPET>
org.codehaus.mojo
dbunit-maven-plugin
mysql
mysql-connector-java
5.0.4
com.mysql.jdbc.Driver
jdbc:mysql://localhost/phonebook
root
root
compile
operation
CLEAN_INSERT
insert.xml
xml
COMPLETE>
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
wicket-stuff
wicket-phonebook
war
1.2
Wicket Phonebook Example
Wicket Phonebook Example - Spring & [Hibernate|iBATIS]
CrUD app
http://wicket.sourceforge.net/
2005
wicket-repo
wicket-repo
http://wicketframework.org/maven2
org.apache.wicket
wicket
1.3-incubating-SNAPSHOT
jar
compile
org.apache.wicket
wicket-extensions
1.3-incubating-SNAPSHOT
jar
compile
org.apache.wicket
wicket-spring
1.3-incubating-SNAPSHOT
jar
compile
cglib
cglib-nodep
org.apache.wicket
wicket-spring-annot
1.3-incubating-SNAPSHOT
jar
compile
org.springframework
spring
2.0.1
org.hibernate
hibernate
3.2.0.ga
compile
com.ibatis
ibatis2-sqlmap
2.1.7.597
mysql
mysql-connector-java
5.0.4
commons-dbcp
commons-dbcp
1.2.1
org.mortbay.jetty
jetty
6.0.1
test
net.sf.shadesdb
shades
0.0.5
org.mortbay.jetty
jetty
6.0.0beta17
compile
net.sourceforge.jwebunit
jwebunit-htmlunit-plugin
1.3
test
src/java
src/test
src/conf
**/*
src/java
**/*
org.apache.maven.plugins
maven-assembly-plugin
src/assembly/bin.xml
${artifactId}-${version}
target/distributions
target/assembly/work
org.apache.maven.plugins
maven-war-plugin
src/webapp
org.apache.maven.plugins
maven-javadoc-plugin
128m
256m
org.apache.maven.plugins
maven-site-plugin
${basedir}/src/site/template/
wicket-site.vm
org.apache.maven.plugins
maven-surefire-plugin
*
[jira] Commented: (MNG-2794) Transitive dependency resolution differs between 2.0.4 and (future) 2.0.5
[ http://jira.codehaus.org/browse/MNG-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87295 ] Jason van Zyl commented on MNG-2794: After looking at this specific case, you are doing something that we do not recommend. If the project you are working has a direct dependency which you require for compilation then you should be specifying it. I realize something has changed, but you should be specifying. And the behavior in 2.0.5 is actually more correct according to our select the nearest strategy. If you rearrange the dependencies and put the dependency that has a dependency on commons-collections 3.0 then the builds works fine. > Transitive dependency resolution differs between 2.0.4 and (future) 2.0.5 > - > > Key: MNG-2794 > URL: http://jira.codehaus.org/browse/MNG-2794 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.5 >Reporter: Fabrice BELLINGARD > Fix For: 2.0.5 > > Attachments: Test-DependencyResolution.zip > > > Say you have a project that has 3 dependecies A, B and C, amongst which 2 of > them have a dependency D but with a different version: > A -> D v2.1 > B -> D v3 > C (has no transitive dependency to D) > In the project, you call a class that exists in D v3 but not in D v2.1. > -> If you launch "mvn clean compile" with M2.0.4, the build is successful, > but not with M2.0.5. > And the most surprising: if you remove dependency C, then both builds break... > I attached a test project that reproduces the bug. -- 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-2589) Inherit transitive dependencies with runtime scope
[ http://jira.codehaus.org/browse/MNG-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2589: --- Fix Version/s: 2.1-alpha-1 > Inherit transitive dependencies with runtime scope > -- > > Key: MNG-2589 > URL: http://jira.codehaus.org/browse/MNG-2589 > Project: Maven 2 > Issue Type: Improvement > Components: Dependencies >Affects Versions: 2.0.4 >Reporter: Joerg Schaible > Fix For: 2.1-alpha-1 > > > Transitive dependencies of scope "compile" should be inherited with scope > "compile" only. This would avoid unwanted usage of 3rd party packages and > make explicit dependencies visible. It should be possible at least to run > Maven in such a mode. -- 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-2589) Inherit transitive dependencies with runtime scope
[ http://jira.codehaus.org/browse/MNG-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MNG-2589: Component/s: Dependencies > Inherit transitive dependencies with runtime scope > -- > > Key: MNG-2589 > URL: http://jira.codehaus.org/browse/MNG-2589 > Project: Maven 2 > Issue Type: Improvement > Components: Dependencies >Affects Versions: 2.0.4 >Reporter: Joerg Schaible > Fix For: 2.1-alpha-1 > > > Transitive dependencies of scope "compile" should be inherited with scope > "compile" only. This would avoid unwanted usage of 3rd party packages and > make explicit dependencies visible. It should be possible at least to run > Maven in such a mode. -- 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: (MRM-278) Unable to un-check checkboxes
[ http://jira.codehaus.org/browse/MRM-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87305 ] Brett Porter commented on MRM-278: -- this is probably my fault > Unable to un-check checkboxes > - > > Key: MRM-278 > URL: http://jira.codehaus.org/browse/MRM-278 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0 > Environment: 1.0-SNAPSHOT, r505337, using 'mvn jetty:run' in > archiva-webapp >Reporter: Wendy Smoak > Assigned To: Brett Porter > > When editing repositories, I am unable to un-check any of the checkboxes, > such as 'Include Snapshots' or 'Use HTTP Proxy'. > The only way I can make changes is to edit ~/.m2/archiva.xml and re-start. -- 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-1380) Please sync with Json-lib repo
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 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] 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_87320 ] Carlos Sanchez commented on MEV-498: no, it's policy not to remove anything unless it's clearly unusable. > 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] Closed: (MNG-2794) Transitive dependency resolution differs between 2.0.4 and (future) 2.0.5
[ http://jira.codehaus.org/browse/MNG-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2794. -- Resolution: Won't Fix The behavior in 2.0.5 is correct and is the behavior we actually have documented. > Transitive dependency resolution differs between 2.0.4 and (future) 2.0.5 > - > > Key: MNG-2794 > URL: http://jira.codehaus.org/browse/MNG-2794 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.5 >Reporter: Fabrice BELLINGARD > Fix For: 2.0.5 > > Attachments: Test-DependencyResolution.zip > > > Say you have a project that has 3 dependecies A, B and C, amongst which 2 of > them have a dependency D but with a different version: > A -> D v2.1 > B -> D v3 > C (has no transitive dependency to D) > In the project, you call a class that exists in D v3 but not in D v2.1. > -> If you launch "mvn clean compile" with M2.0.4, the build is successful, > but not with M2.0.5. > And the most surprising: if you remove dependency C, then both builds break... > I attached a test project that reproduces the bug. -- 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: (MRM-277) Proxied repositories change order when edited
[ http://jira.codehaus.org/browse/MRM-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87323 ] Brett Porter commented on MRM-277: -- I suggest adding sorting by 'Name' so that the configuration and page are always consistently ordered. > Proxied repositories change order when edited > - > > Key: MRM-277 > URL: http://jira.codehaus.org/browse/MRM-277 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0 > Environment: 1.0-SNAPSHOT, r505337 >Reporter: Wendy Smoak > Assigned To: Brett Porter >Priority: Minor > > If you edit a proxied repository (to check/uncheck 'Use HTTP Proxy' for > example) the order of the list changes after you update. > To reproduce, set up more than one proxied repository, then: > 1. Administration -> Proxied Repositories > 2. Observe the order of the list of proxied repositories > 3. Edit Repository -> (make a change) -> Update Repository > 4. Compare the order of the list to (2) > They should always be in the same order. -- 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_87328 ] Dan Tran commented on MEV-498: -- I beleive it is unuable since the the jaxws-api at java.net has the correct dependencies and the jar at jaxws-api at java.net has more interfaces. The user of jaxws-maven-plugin is blocked from using this plugin since jaxws-api at repo1 is picked up first. > 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] Closed: (MRM-278) Unable to un-check checkboxes
[ http://jira.codehaus.org/browse/MRM-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-278. Resolution: Fixed > Unable to un-check checkboxes > - > > Key: MRM-278 > URL: http://jira.codehaus.org/browse/MRM-278 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0 > Environment: 1.0-SNAPSHOT, r505337, using 'mvn jetty:run' in > archiva-webapp >Reporter: Wendy Smoak > Assigned To: Brett Porter > > When editing repositories, I am unable to un-check any of the checkboxes, > such as 'Include Snapshots' or 'Use HTTP Proxy'. > The only way I can make changes is to edit ~/.m2/archiva.xml and re-start. -- 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_87330 ] Carlos Sanchez commented on MEV-498: The fact that it's incorrect doesn't make it unusable. Unusable means jar corrupt or empty. wdym about jaxws-maven-plugin problem? the central repo has to be self contained, the plugin can't be releasing depending on stuff in other repos > 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] 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_87337 ] Dan Tran commented on MEV-498: -- jaxws-maven-plugin is in an odd situation where most of its dependencies are in java.net maven1 repo. One of the dependency (jaxws-api) happen to be at repo1 as well. Since repo1 is primary repo, its jaxws-api is picked up first and therefore jaxws-maven-plugin is unusable. 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. Question, why does repo1 have a deployment of jaxws-2.1 way before it is official released? > 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
