[jira] Commented: (NMAVEN-84) Reseach feasability of SHFB plugin
[ http://jira.codehaus.org/browse/NMAVEN-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116905 ] Shane Isbell commented on NMAVEN-84: Is this something that we should close out? > Reseach feasability of SHFB plugin > -- > > Key: NMAVEN-84 > URL: http://jira.codehaus.org/browse/NMAVEN-84 > Project: NMaven > Issue Type: Sub-task >Reporter: Campbell Boucher-Burnet >Priority: Minor > -- 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-84) Reseach feasability of SHFB plugin
[ http://jira.codehaus.org/browse/NMAVEN-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated NMAVEN-84: --- Priority: Minor (was: Major) > Reseach feasability of SHFB plugin > -- > > Key: NMAVEN-84 > URL: http://jira.codehaus.org/browse/NMAVEN-84 > Project: NMaven > Issue Type: Sub-task >Reporter: Campbell Boucher-Burnet >Priority: Minor > -- 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-42) Conversion from a csproj File to a pom.xml File
[ http://jira.codehaus.org/browse/NMAVEN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated NMAVEN-42: --- Priority: Minor (was: Major) > Conversion from a csproj File to a pom.xml File > --- > > Key: NMAVEN-42 > URL: http://jira.codehaus.org/browse/NMAVEN-42 > Project: NMaven > Issue Type: New Feature >Reporter: Shane Isbell >Priority: Minor > > The framework should support converting from a csproject file to a pom. This > has two advantages: 1) recovering from a corrupted or outdated pom (one that > is older than the csproject file) and 2) helping to transition existing > projects to NMaven. -- 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-83) NUnit compile time assemblies and runtime assemblies can become out of sync
[ http://jira.codehaus.org/browse/NMAVEN-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-83. -- Resolution: Won't Fix Use plugin parameter to solve problem. > NUnit compile time assemblies and runtime assemblies can become out of sync > --- > > Key: NMAVEN-83 > URL: http://jira.codehaus.org/browse/NMAVEN-83 > Project: NMaven > Issue Type: Improvement > Environment: Maven 2.0.6, Windows XP, NMaven 0.14-SNAPSHOT >Reporter: Evan Worley >Priority: Minor > > NMaven compiles the test assembly using the NUnit assemblies that are in the > GAC or local repository. When the tests are executed nunit-console ran from > the command line assuming that is exists on your path. If you are using > nunit-console with nunit runtime assemblies that are of a different version > than the assemblies used at compile time, your tests will not executed. If > you manually run nunit-console to verify the issue you will see a message > like the following, > >nunit-console IntegrationTest-test.dll > NUnit version 2.2.8 > Copyright (C) 2002-2003 James W. Newkirk, Michael C. Two, Alexei A. > Vorontsov, Charlie Poole. > Copyright (C) 2000-2003 Philip Craig. > All Rights Reserved. > OS Version: Microsoft Windows NT 5.1.2600.0.NET Version: 1.1.4322.2032 > The format of the file 'IntegrationTest-test' is invalid. -- 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-79) With MICROSOFT still failing with "NMAVEN-9011-007: Mono installation could not be found."
[ http://jira.codehaus.org/browse/NMAVEN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-79. -- Resolution: Fixed Fix Version/s: 0.14 > With MICROSOFT still failing with "NMAVEN-9011-007: Mono > installation could not be found." > --- > > Key: NMAVEN-79 > URL: http://jira.codehaus.org/browse/NMAVEN-79 > Project: NMaven > Issue Type: Bug > Environment: ALLUSERSPROFILE=C:\Documents and Settings\All Users > APPDATA=C:\Documents and Settings\bdeacon\Application Data > ASMROOT=C:\TNGSD\SD > CLASSPATH=.;C:\Program Files\Java\jre1.5.0_11\lib\ext\QTJava.zip > CLIENTNAME=Console > CommonProgramFiles=C:\Program Files\Common Files > COMPUTERNAME=SDGD04202608 > ComSpec=C:\WINDOWS\system32\cmd.exe > CVSROOT=:pserver:[EMAIL PROTECTED]:/v/releng/cvsroot > ERROR_CODE=1 > FP_NO_HOST_CHECK=NO > HOMEDRIVE=H: > HOMEPATH=\ > HOMESHARE=\\sdgfs01\users\bdeacon > Intuit=1 > JAVA_HOME=C:\Program Files\Java\jdk1.5.0_12 > LOGONSERVER=\\SDGDCCORP04 > M2_HOME=C:\Program Files\Apache Software Foundation\maven-2.0.6 > MAVEN_HOME=C:\Program Files\Apache Software Foundation\Maven 1.0.2 > MSILIB=\\SDPSDO05\MSILIB > NUMBER_OF_PROCESSORS=2 > OS=Windows_NT > Path=C:\Program > Files\Java\jdk1.5.0_12\bin;C:\Perl\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\Downloaded > Program Files;C:\Program Files\Common Files\Roxio > Shared\DLLShared;C:\TNGSD\BIN;c:\Program Files\Microsoft SQL > Server\90\Tools\binn\;C:\utils\bin;C:\Program Files\Apache Software > Foundation\Maven 1.0.2\bin;C:\Program Files\Apache Software > Foundation\maven-2.0.6\bin;C:\Program Files\cvsnt;C:\Program > Files\Perforce;C:\Program Files\IDM Computer > Solutions\UltraEdit-32;C:\mysql5\bin;C:\ruby\bin;C:\Program > Files\QuickTime\QTSystem\ > PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH > PROCESSOR_ARCHITECTURE=x86 > PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 1, GenuineIntel > PROCESSOR_LEVEL=15 > PROCESSOR_REVISION=0401 > ProgramFiles=C:\Program Files > PROMPT=$P$G > QTJAVA=C:\Program Files\Java\jre1.5.0_11\lib\ext\QTJava.zip > RUBYOPT=rubygems > RUBY_HOME=C:\ruby > SESSIONNAME=Console > SystemDrive=C: > SystemRoot=C:\WINDOWS > TEMP=C:\TEMP > TMP=C:\TEMP > USERDNSDOMAIN=CORP.INTUIT.NET > USERDOMAIN=CORP > USERNAME=bdeacon > USERPROFILE=C:\Documents and Settings\bdeacon > VS80COMNTOOLS=C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\ > windir=C:\WINDOWS >Reporter: Brian Deacon > Fix For: 0.14 > > Attachments: build.log, pom.xml, SettingsGeneratorMojo.diff, > SettingsGeneratorMojo.diff > > > Pom and log output attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (NMAVEN-93) NMaven requires admin privs on Vista to build
[ http://jira.codehaus.org/browse/NMAVEN-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-93. -- Resolution: Won't Fix > NMaven requires admin privs on Vista to build > - > > Key: NMAVEN-93 > URL: http://jira.codehaus.org/browse/NMAVEN-93 > Project: NMaven > Issue Type: Bug >Reporter: Brett Porter > > I'm unclear on why installing to the GAC is required simply to build NMaven - > and this causes the build to fail unless you run at elevated privileges on > Vista. > Is there a way this requirement could be avoided? -- 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-52) As Part of Life-Cycle NMaven Should Verify That All Assemblies in Local Repo Are Valid
[ http://jira.codehaus.org/browse/NMAVEN-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-52. -- Resolution: Won't Fix > As Part of Life-Cycle NMaven Should Verify That All Assemblies in Local Repo > Are Valid > -- > > Key: NMAVEN-52 > URL: http://jira.codehaus.org/browse/NMAVEN-52 > Project: NMaven > Issue Type: Improvement >Reporter: Shane Isbell >Priority: Minor > > As part of the life-cycle NMaven should verify that all assemblies entering > the local repo (through resolving from a remote repo) and exiting the repo > (deploying) are valid assemblies. -- 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-86) Code sketch for NMaven.Model.Settings support, as well as a non-trivial application thereof in the visual studio addin connect method.
[ http://jira.codehaus.org/browse/NMAVEN-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-86. -- Resolution: Fixed Fix Version/s: 0.14 > Code sketch for NMaven.Model.Settings support, as well as a non-trivial > application thereof in the visual studio addin connect method. > --- > > Key: NMAVEN-86 > URL: http://jira.codehaus.org/browse/NMAVEN-86 > Project: NMaven > Issue Type: Improvement > Environment: N/A >Reporter: Campbell Boucher-Burnet >Priority: Minor > Fix For: 0.14 > > Attachments: nmaven-2007-08-30-campbell.patch.zip > > > In the course of using NMaven, it has become evident that a ubiquitous, > runtime facility for discovering the local maven repository path (and other > settings.xml provided information) is essential. > A patch to get started down this road is provided. -- 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-71) Replace various hard-coded paths with environment-aware versions
[ http://jira.codehaus.org/browse/NMAVEN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-71. -- Resolution: Fixed Fix Version/s: 0.14 > Replace various hard-coded paths with environment-aware versions > > > Key: NMAVEN-71 > URL: http://jira.codehaus.org/browse/NMAVEN-71 > Project: NMaven > Issue Type: Improvement > Environment: Windows? >Reporter: Campbell Boucher-Burnet >Priority: Blocker > Fix For: 0.14 > > Attachments: patches.zip > > > I'm in an environment where my system drive is not "C:\" and I cannot > guarantee that all .NET related libraries/SDKs are on "C:\" in their default > locations. > As such, it was impossible to build NMavewn (and presumably, the binaries, as > built by default, would not work in my environment, regardless). > So, I am submitting minimal patches that replace hardcoded strings containing > "C:\WINDOWS" and" C:\", respectively, with the SystemRoot and SystemDrive > paths from the enviroment. -- 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-98) Dotnet simple archetype does not include unit tests
[ http://jira.codehaus.org/browse/NMAVEN-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-98. -- Resolution: Fixed Fix Version/s: 0.14 > Dotnet simple archetype does not include unit tests > --- > > Key: NMAVEN-98 > URL: http://jira.codehaus.org/browse/NMAVEN-98 > Project: NMaven > Issue Type: Improvement >Reporter: Teodoro Cue Jr. > Fix For: 0.14 > > Attachments: NMAVEN-98.patch > > > Building a project created from the dotnet-simple archetype produces: > [INFO] [compile:testCompile] > [INFO] NMAVEN-066-013: Found Vendor = Vendor = MICROSOFT, Vendor Version = > 2.0.5 > 0727, Framework Version = 2.0.50727, Executable Paths = > [C:\WINDOWS\Microsoft.NE > T\Framework\v2.0.50727] > [INFO] NMAVEN-068-002: No source files to compile. > [INFO] Mojo Execution Time = 0 > [INFO] [test:test] > [INFO] NMAVEN-1100-001: No Unit Tests > The dotnet-simple archetype should include an NUnit test case. -- 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-56) Cannot run NUnit tests independen
[ http://jira.codehaus.org/browse/NMAVEN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-56. -- Resolution: Fixed Fix Version/s: 0.14 > Cannot run NUnit tests independen > - > > Key: NMAVEN-56 > URL: http://jira.codehaus.org/browse/NMAVEN-56 > Project: NMaven > Issue Type: Bug >Reporter: zak jacobson > Fix For: 0.14 > > > Executing org.apache.maven.dotnet.plugins:maven-test-plugin:test causes > exception: > java.lang.NullPointerException > at > org.apache.maven.dotnet.plugin.test.TesterMojo.execute(TesterMojo.java:140) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- 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-91) Repository plugin export-rdf goal only works in a directory containing a pom
[
http://jira.codehaus.org/browse/NMAVEN-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Isbell closed NMAVEN-91.
--
Resolution: Won't Fix
> Repository plugin export-rdf goal only works in a directory containing a pom
>
>
> Key: NMAVEN-91
> URL: http://jira.codehaus.org/browse/NMAVEN-91
> Project: NMaven
> Issue Type: Bug
>Reporter: Wendy Smoak
>
> The "mvn org.apache.maven.dotnet.plugins:maven-repository-plugin:export-rdf"
> command explained on [1] apparently only works in a directory containing a
> pom.xml file.
> {noformat}
> C:\Temp>mvn org.apache.maven.dotnet.plugins:maven-repository-plugin:export-rdf
> [INFO]
> -
> ---
> [INFO] Building Maven Default Project
> [INFO]task-segment:
> [org.apache.maven.dotnet.plugins:maven-repository-plugin:export-rdf]
> [INFO]
>
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Cannot execute mojo: export-rdf. It requires a project with an
> existing pom.xml, but the build is not using one.
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 1 second
> [INFO] Finished at: Mon Oct 29 14:39:38 MST 2007
> [INFO] Final Memory: 1M/4M
> [INFO]
>
> {noformat}
> I'm having trouble installing the Visual Studio addin. I'm not working with
> "a project".
> If this can't be changed, the documentation should be updated to explain the
> issue and provide a simple pom.xml file that can be saved in the current
> directory to allow the command to work.
> [1] http://incubator.apache.org/nmaven/rdf-repository.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (NMAVEN-19) Dependency resolution and Maven integration (site, deploy)
[ http://jira.codehaus.org/browse/NMAVEN-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-19. -- Resolution: Fixed > Dependency resolution and Maven integration (site, deploy) > -- > > Key: NMAVEN-19 > URL: http://jira.codehaus.org/browse/NMAVEN-19 > Project: NMaven > Issue Type: Wish >Reporter: Alexandre Garcia > Attachments: components.patch > > > First of all Shane, we really appreciate your effort. > We tried to complement your packaging lifecycles in order to test site and > deploy > The Maven plugins site and deploy use the standard Maven artefact layout: > ArtefactId-Version.dll > We were able to use mvn site after renaming accordingly installed artefacts > in the local repo ($reports is not expanded though). > We rebuilt NMaven after altering > NMaven\plugins\maven-compile-plugin\src\main\resources\META-INF\plexus\components.xml > to include the deploy phase in the packaging lifecycles. > The deploy phase is successful but is once again maven style. > Unfortunately, the deployed artefacts cannot be downloaded because NMaven > dependency resolution doesnot include the version suffix and hence doesnot > find the artefact on the remote repo. > More generally, i wish NMaven could adopt default Maven style artefact layout > or a mixed mode for GAC dependencies. > We attach the modified components.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] Closed: (NMAVEN-28) -SNAPSHOT suffixed version in generated AssemblyInfo for library snapshot version
[ http://jira.codehaus.org/browse/NMAVEN-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-28. -- Resolution: Fixed Fix Version/s: 0.14 > -SNAPSHOT suffixed version in generated AssemblyInfo for library snapshot > version > - > > Key: NMAVEN-28 > URL: http://jira.codehaus.org/browse/NMAVEN-28 > Project: NMaven > Issue Type: Bug >Reporter: Alexandre Garcia > Fix For: 0.14 > > > In the generated AssemblyInfo.cs, the snapshot version is placed as is, with > the -SNAPSHOT suffix. > Compilation fails. -- 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-50) Verify Assembly's Public Key Token Before Installing into GAC
[ http://jira.codehaus.org/browse/NMAVEN-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated NMAVEN-50: --- Priority: Minor (was: Major) > Verify Assembly's Public Key Token Before Installing into GAC > - > > Key: NMAVEN-50 > URL: http://jira.codehaus.org/browse/NMAVEN-50 > Project: NMaven > Issue Type: Improvement >Reporter: Shane Isbell >Priority: Minor > > Verify assembly's public key token matches PublicKeyToken entry in > net-executables.xml file, prior to installing assembly into the GAC. -- 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-59) IDE Output Pane Only Displays the Maven Java Output
[ http://jira.codehaus.org/browse/NMAVEN-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated NMAVEN-59: --- Priority: Minor (was: Major) > IDE Output Pane Only Displays the Maven Java Output > --- > > Key: NMAVEN-59 > URL: http://jira.codehaus.org/browse/NMAVEN-59 > Project: NMaven > Issue Type: Bug >Reporter: Shane Isbell >Priority: Minor > > The maven embedder only writes Maven (Java) output to the IDE output pane.. > The .NET generated console output also needs to be written to the IDE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (NMAVEN-51) Remove Hard-Coded Local Repository Path in Visual Studio Solution Plugin
[ http://jira.codehaus.org/browse/NMAVEN-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-51. -- Resolution: Fixed > Remove Hard-Coded Local Repository Path in Visual Studio Solution Plugin > > > Key: NMAVEN-51 > URL: http://jira.codehaus.org/browse/NMAVEN-51 > Project: NMaven > Issue Type: Improvement >Reporter: Shane Isbell >Priority: Minor > > The visual studio solution plugin (in .NET) contains a hard-coded value for > the local repository. This can be fixed by adding a local repository > attribute to the solution plugin and passing that to the NMaven.Core > assembly. -- 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-60) Maven Generated IDE Solution and Project Files Contain Hard-Coded Values
[ http://jira.codehaus.org/browse/NMAVEN-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-60. -- Resolution: Won't Fix > Maven Generated IDE Solution and Project Files Contain Hard-Coded Values > > > Key: NMAVEN-60 > URL: http://jira.codehaus.org/browse/NMAVEN-60 > Project: NMaven > Issue Type: Bug >Reporter: Shane Isbell > > Maven generated IDE solution and project files contain hard-coded values. > This is a problem for checking in and checkout out solution files into a > version control system. -- 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-69) Replace Existing Logging Component with Log4net
[ http://jira.codehaus.org/browse/NMAVEN-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-69. -- Resolution: Won't Fix Current logging works fine. > Replace Existing Logging Component with Log4net > --- > > Key: NMAVEN-69 > URL: http://jira.codehaus.org/browse/NMAVEN-69 > Project: NMaven > Issue Type: Improvement >Reporter: Shane Isbell > > Replace existing logging component with Log4net: 1) replacing Console > statements with log4net statements; 2) importing of log4net libs during > build; 3) dumping the existing NMaven logging component (based on > java.util.logging) that handles the logging for both VS and SD. -- 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-37) Support VSI Packaging for Visual Studio Content Installer
[ http://jira.codehaus.org/browse/NMAVEN-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-37. -- Resolution: Won't Fix This is not needed. The vsinstaller plugin handles installing of addin. > Support VSI Packaging for Visual Studio Content Installer > --- > > Key: NMAVEN-37 > URL: http://jira.codehaus.org/browse/NMAVEN-37 > Project: NMaven > Issue Type: New Feature > Environment: Microsoft, Visual Studio >Reporter: Shane Isbell >Priority: Minor > > The feature involves creating a .vscontent file and zipping up all the > assemblies. I need this feature for packaging of the NMaven Add-In for VS. -- 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-62) Snapshots not supported in assemblies compiled from Java or VB.
[ http://jira.codehaus.org/browse/NMAVEN-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-62. -- Resolution: Fixed > Snapshots not supported in assemblies compiled from Java or VB. > --- > > Key: NMAVEN-62 > URL: http://jira.codehaus.org/browse/NMAVEN-62 > Project: NMaven > Issue Type: Bug >Reporter: Shane Isbell >Priority: Minor > > Snapshots are not supported in assemblies compiled from Java or VB. -- 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-27) Inconsistent Base Directories Used For Executable Plugins
[
http://jira.codehaus.org/browse/NMAVEN-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Isbell closed NMAVEN-27.
--
Resolution: Won't Fix
executable plugins have been deprecated.
> Inconsistent Base Directories Used For Executable Plugins
> -
>
> Key: NMAVEN-27
> URL: http://jira.codehaus.org/browse/NMAVEN-27
> Project: NMaven
> Issue Type: Bug
>Reporter: Shane Isbell
>
> Executables often have input files. Say a user's executable references
> (through the plugin configuration) a file as myfile.txt. If the executable
> only exists on the PATH (in other words it is not found in a standard .NET
> framework directory), then the file URI resolves to ${basedir}/myfile.txt. If
> the executable exists in the .NET framework directory, it resolves to
> ${install_root}/myfile.txt. Work Around: Explicitly set the location of the
> file, either through an absolute URL or by explicitly using the ${basedir}
> parameter.
--
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-33) Support for Compiler/Executable Archetypes
[ http://jira.codehaus.org/browse/NMAVEN-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-33. -- Resolution: Won't Fix All of the xml data associated with this request has been deprecated. > Support for Compiler/Executable Archetypes > -- > > Key: NMAVEN-33 > URL: http://jira.codehaus.org/browse/NMAVEN-33 > Project: NMaven > Issue Type: New Feature >Reporter: Shane Isbell >Priority: Minor > > Adding compilers and executables to NMaven has become standard enough that I > would like to create a plugin for automatically generating > compiler/executable projects. This would allow developers to easily add new > languages and executables (xsd, wsdl, etc) to the framework. This feature > should also allow the modification of existing projects (for use when adding > new functionality to dotnet core). > The implementation largely deals with modifying (or creating) > compile-plugins.xml, executable-plugins.xml and assembly-plugins.xml and with > creating of CompilerExecutable stubs. -- 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-74) Maven Deploy Plugin Does Not Support exe.config files
[ http://jira.codehaus.org/browse/NMAVEN-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-74. -- Resolution: Fixed > Maven Deploy Plugin Does Not Support exe.config files > - > > Key: NMAVEN-74 > URL: http://jira.codehaus.org/browse/NMAVEN-74 > Project: NMaven > Issue Type: Bug >Reporter: Shane Isbell >Priority: Critical > > The deploy plugin does not deploy exe.config files. This causes any resolving > of NMaven from a remote repo to fail. As a temporary work around, I manually > placed the file in the snapshot repo. -- 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-36) Need a Way to Determine if a Maven Plugin Defined Within a Lifecycle Mapping Phase Should Execute Based on Vendor Info
[ http://jira.codehaus.org/browse/NMAVEN-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-36. -- Resolution: Won't Fix Vendor info and matching no longer supported. > Need a Way to Determine if a Maven Plugin Defined Within a Lifecycle Mapping > Phase Should Execute Based on Vendor Info > -- > > Key: NMAVEN-36 > URL: http://jira.codehaus.org/browse/NMAVEN-36 > Project: NMaven > Issue Type: Improvement >Reporter: Shane Isbell >Priority: Minor > > Currently, DotGNU does not support the resgen plugin. This plugin is executed > withing a phase of the core lifecycle mapping. Need a way for NMaven to > determine whether it should execute a plugin based on vendor info: version, > framework, vendor. -- 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-70) Support for executing maven command lines from IDE
[ http://jira.codehaus.org/browse/NMAVEN-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-70. -- Resolution: Won't Fix > Support for executing maven command lines from IDE > -- > > Key: NMAVEN-70 > URL: http://jira.codehaus.org/browse/NMAVEN-70 > Project: NMaven > Issue Type: New Feature > Environment: Visual Studio 2005 >Reporter: Shane Isbell >Priority: Minor > > Add support for executing maven command lines from IDE. This would be a > console in VS that would allow the user to type in a mvn command and have it > executed (with the results displaying in the output pane). -- 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-80) Support for batch builds of multiple projects in VIsual Studio 2005
[ http://jira.codehaus.org/browse/NMAVEN-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-80. -- Resolution: Won't Fix > Support for batch builds of multiple projects in VIsual Studio 2005 > > > Key: NMAVEN-80 > URL: http://jira.codehaus.org/browse/NMAVEN-80 > Project: NMaven > Issue Type: Improvement > Environment: Windows >Reporter: Shane Isbell >Priority: Minor > > The user should be able to select multiple projects within VIsual Studio 2005 > and have NMaven build them as a batch. NMaven should be able to resolve the > dependency order dynamically. -- 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-65) Investigate Changing the Packaging Types to Prevent Name Conflicts
[ http://jira.codehaus.org/browse/NMAVEN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-65. -- Resolution: Fixed Decided to move to dotnet: convention. > Investigate Changing the Packaging Types to Prevent Name Conflicts > -- > > Key: NMAVEN-65 > URL: http://jira.codehaus.org/browse/NMAVEN-65 > Project: NMaven > Issue Type: Task >Reporter: Shane Isbell >Priority: Minor > > Currently the primary types include: library, exe, winexe, netmodule. Some of > these may conflict with future Maven language support projects. Investigate > options. -- 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-25) Platform Capability Matching for Third-Party Programs Installed On The Build Platform
[ http://jira.codehaus.org/browse/NMAVEN-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-25. -- Resolution: Won't Fix Platform capability matching has been deprecated. > Platform Capability Matching for Third-Party Programs Installed On The Build > Platform > - > > Key: NMAVEN-25 > URL: http://jira.codehaus.org/browse/NMAVEN-25 > Project: NMaven > Issue Type: New Feature > Environment: Microsoft, Mono, Windows, Linux >Reporter: Shane Isbell >Priority: Minor > > Some executables are only available with third-party programs such as Visual > Studio or NUnit. The platform capability/requirement matching framework > should be able to handle detecting these programs and deciding 1) if the > Maven plugin is allowed to execute; 2) if so, the location of the executable > on the file system. This solution will require a "program detector" that a > plugin developer can configure to check directories and/or the Windows > Registry for program presence. -- 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-61) Can't Compile Sharp Develop IDE Addin As Part of Standard-Build Since the Dependent Libraries Can't be Redistributed
[ http://jira.codehaus.org/browse/NMAVEN-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-61. -- Resolution: Won't Fix > Can't Compile Sharp Develop IDE Addin As Part of Standard-Build Since the > Dependent Libraries Can't be Redistributed > > > Key: NMAVEN-61 > URL: http://jira.codehaus.org/browse/NMAVEN-61 > Project: NMaven > Issue Type: Improvement > Environment: SharpDevelop >Reporter: Shane Isbell > > Can't compile sharp develop IDE addin as part of standard-build since the > dependent libraries can't be redistributed. I need to install dependent > libraries into the repo (or GAC) so that NMaven can build the addin, but the > developer must somehow indicate the location of the SharpDevelop root. -- 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-57) Generated nmaven-settings file should specify Mono as the default vendor when -Dvendor=MONO is specified within the first build of the system
[ http://jira.codehaus.org/browse/NMAVEN-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-57. -- Resolution: Won't Fix nmaven-settings file has been deprecated. > Generated nmaven-settings file should specify Mono as the default vendor when > -Dvendor=MONO is specified within the first build of the system > - > > Key: NMAVEN-57 > URL: http://jira.codehaus.org/browse/NMAVEN-57 > Project: NMaven > Issue Type: Bug > Environment: Windows >Reporter: Shane Isbell >Priority: Minor > > Prior to a user first building with NMaven, there is no nmaven-settings.xml > file. When the user types, say mvn install from the command-line, NMaven will > generate the settings file and will specify Microsoft framework - provided > that it is installed - as the default build framework. If a user, however, > has both Microsoft and Mono installed and then types, mvn install > -Dvendor=MONO, the project will compile with Mono but the default setup in > the settings file will specify MICROSOFT as the default vendor: the default > setup should specify Mono as a convenience to the user. > This issue does not exist if only Mono is installed on the build platform. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (NMAVEN-39) Browse Maven Repository and Add/Delete Dependencies through the IDE
[ http://jira.codehaus.org/browse/NMAVEN-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-39. -- Resolution: Fixed Fix Version/s: 0.14 > Browse Maven Repository and Add/Delete Dependencies through the IDE > --- > > Key: NMAVEN-39 > URL: http://jira.codehaus.org/browse/NMAVEN-39 > Project: NMaven > Issue Type: New Feature > Environment: Windows, Linux, Visual Studio, Sharp Develop >Reporter: Shane Isbell > Fix For: 0.14 > > > The developer should be able to browse local and remote repositories and > attach/delete dependencies (including transitive) to both the IDE project > file and the 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] Closed: (NMAVEN-48) Packaging and Deploying for Sharp Develop Addins
[ http://jira.codehaus.org/browse/NMAVEN-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-48. -- Resolution: Won't Fix Doesn't appear to be much community interest in supporting SharpDevelop as an IDE. > Packaging and Deploying for Sharp Develop Addins > - > > Key: NMAVEN-48 > URL: http://jira.codehaus.org/browse/NMAVEN-48 > Project: NMaven > Issue Type: New Feature > Environment: Sharp Develop >Reporter: Shane Isbell >Priority: Minor > > The feature should include support for generation the sharp develop addin XML > file and for putting the XML addin file (and associated resources) within the > appropriate directory for the IDE to read. -- 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-2) NMaven Support for Classifiers
[ http://jira.codehaus.org/browse/NMAVEN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-2. - Resolution: Fixed > NMaven Support for Classifiers > -- > > Key: NMAVEN-2 > URL: http://jira.codehaus.org/browse/NMAVEN-2 > Project: NMaven > Issue Type: Improvement >Reporter: Shane Isbell >Priority: Minor > > NMaven should support classifiers to allow: 1) multiple builds (depending on > framework) of the NMaven .NET assembly plugins; 2) the use of 3rd party > assemblies that target a specific framework version. Support may require a > change with Maven core. One possible approach would be that whatever methods > (within Maven core) that are invoking > ArtifactRepositoryLayout.pathOf(pomArtifact) should set the classifier > information within the pomArtifact. > To provide context of this issue, I prototyped a version of NMaven that > supported classifiers but ran into an issue with Maven. NMaven does not put > meta-data - like the version or classifier - in the file name but rather > within the artifact directory structure. In the case of version, this is > fairly easy to handle because both the pomArtifact and the binaryArtifact > contain the version information: the ArtifactRepositoryLayout.pathOf method > can append the version to the artifact path. In the case of classifier, the > pomArtifact does not contain the classifier information ( > artifact.getClassifier() returns null): the ArtifactRepositoryLayout.pathOf > method has no way to append the classifier to the artifact path for the pom. > Thus under the current Maven version, we are unable to handle transitive > dependencies for artifacts with classifiers (due to not finding the pom > artifact). -- 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-54) Support for Attaching Platform Metadata to Assemblies
[ http://jira.codehaus.org/browse/NMAVEN-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-54. -- Resolution: Won't Fix net-dependencies.xml and capability matching support has been deprecated. > Support for Attaching Platform Metadata to Assemblies > - > > Key: NMAVEN-54 > URL: http://jira.codehaus.org/browse/NMAVEN-54 > Project: NMaven > Issue Type: New Feature >Reporter: Shane Isbell >Priority: Minor > > This feature is a superset of classifer support. It will allow the developer > to attach meta-data to the assembly, specifying a range of information, > including targeted platform, OS, architecture, vendor, vendor version, > framework version, java version, as well as custom attributes. Most of this > info is already used within the compiler component but we now need a way for > discovery and resolving of dependent assemblies based on this same info. > Most likely, this will be an expansion of the net-dependencies.xml file. > NMaven would need to look through an assemblies meta-data within the > net-dependencies.xml file to decide if it should be included within a > compile, test, resolve, etc. -- 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-76) NMaven attempts to download direct GAC Dependencies
[ http://jira.codehaus.org/browse/NMAVEN-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-76. -- Resolution: Fixed Fix Version/s: 0.14 > NMaven attempts to download direct GAC Dependencies > --- > > Key: NMAVEN-76 > URL: http://jira.codehaus.org/browse/NMAVEN-76 > Project: NMaven > Issue Type: Bug >Reporter: Shane Isbell >Priority: Minor > Fix For: 0.14 > > > NMaven attempts to download direct GAC Dependencies. This is not a critical > bug but introduces a performance penalty due to the latency from the network > call. -- 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-41) Configuration of Remote Services through the IDE
[ http://jira.codehaus.org/browse/NMAVEN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-41. -- Resolution: Fixed Fix Version/s: 0.14 > Configuration of Remote Services through the IDE > > > Key: NMAVEN-41 > URL: http://jira.codehaus.org/browse/NMAVEN-41 > Project: NMaven > Issue Type: New Feature > Environment: Visual Studio, Sharp Develop >Reporter: Shane Isbell > Fix For: 0.14 > > > The developer will be able to add/delete remote/local repository access > through the IDE. This action would modify the repository tag in the pom.xml > and is also used in conjunction with NMaven-39, where the developer can then > add a dependency from the repo to the project. > This feature also includes the ability to change which MavenEmbedder to use > for the IDE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (NMAVEN-32) .NET Resource Plugin Does Not Compile Under DotGNU
[ http://jira.codehaus.org/browse/NMAVEN-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-32. -- Resolution: Fixed > .NET Resource Plugin Does Not Compile Under DotGNU > -- > > Key: NMAVEN-32 > URL: http://jira.codehaus.org/browse/NMAVEN-32 > Project: NMaven > Issue Type: Bug > Environment: Portable.NET 0.7.2, Windows >Reporter: Shane Isbell > > The .NET resource plugin does not compile under DotGNU compiler. Need to fix > the build to disable this plugin when compiling under DotGNU. -- 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-35) .NET Client For Continuum
[ http://jira.codehaus.org/browse/NMAVEN-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-35. -- Resolution: Won't Fix Continuum does not currently support remote interfaces for clients to interface with. > .NET Client For Continuum > - > > Key: NMAVEN-35 > URL: http://jira.codehaus.org/browse/NMAVEN-35 > Project: NMaven > Issue Type: New Feature >Reporter: Shane Isbell >Priority: Minor > > Create a .NET Client For Continuum. The client will support the standard > operations: addProject, editProject, buildProject, refreshProject, > readProjects -- 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-31) Mono Support for VB
[ http://jira.codehaus.org/browse/NMAVEN-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-31. -- Resolution: Fixed > Mono Support for VB > --- > > Key: NMAVEN-31 > URL: http://jira.codehaus.org/browse/NMAVEN-31 > Project: NMaven > Issue Type: New Feature >Reporter: Shane Isbell >Priority: Minor > > Mono now supports VB (as of version 1.2.3): > http://www.mono-project.com/VisualBasic.NET_support. This merely requires > adding the entry in the compiler-plugins.xml file (but also some setup and > testing). -- 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-82) Support for IoC Container
[ http://jira.codehaus.org/browse/NMAVEN-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-82. -- Resolution: Fixed Fix Version/s: 0.14 Using castle for VS addin. > Support for IoC Container > - > > Key: NMAVEN-82 > URL: http://jira.codehaus.org/browse/NMAVEN-82 > Project: NMaven > Issue Type: New Feature >Reporter: Shane Isbell > Fix For: 0.14 > > > Need to add support for IoC container for use within the NMaven projects. > Currently investigating the use of the MicroKernel from > http://www.castleproject.org/. They use ASL 2.0 license so it is compatible. -- 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-30) Support for Using Vendor Version to Match Compilers and Executables
[ http://jira.codehaus.org/browse/NMAVEN-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-30. -- Resolution: Won't Fix Vendor matching has been deprecated. > Support for Using Vendor Version to Match Compilers and Executables > --- > > Key: NMAVEN-30 > URL: http://jira.codehaus.org/browse/NMAVEN-30 > Project: NMaven > Issue Type: New Feature > Environment: Mono >Reporter: Shane Isbell >Priority: Minor > > Need support for using vendor version to match compilers and executables. > This is needed specifically because Mono introduces new .NET features in each > release: for example, VB support in Mono release 1.2.3. This feature would > allow the user to specify say VB as a language and unless NMaven finds the > right vendor version for Mono, it will fail the build. Support for version > ranges will also be needed. > In the case of MS, we don't need this feature because framework version is > always equals to vendor 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: (NMAVEN-53) Creating New .NET Maven Plugins Should Not Require Adding an Entry within NMaven's net-dependencies.xml File
[ http://jira.codehaus.org/browse/NMAVEN-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-53. -- Resolution: Won't Fix The net-dependencies.xml support has been deprecated. > Creating New .NET Maven Plugins Should Not Require Adding an Entry within > NMaven's net-dependencies.xml File > > > Key: NMAVEN-53 > URL: http://jira.codehaus.org/browse/NMAVEN-53 > Project: NMaven > Issue Type: New Feature >Reporter: Shane Isbell > > The net-dependencies.xml file is used internally for NMaven to resolve .NET > assemblies and .NET Maven plugins. Third-Party developers should be able to > create there own net-dependencies.xml file (this would probably be > auto-generated as part of the plugin generation) and have it read by NMaven. > As it stands now, they have to either recompile NMaven or unjar dotnet-core, > change the file and then repackage. -- 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-21) Support for Ruby .NET Compiler
[ http://jira.codehaus.org/browse/NMAVEN-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-21. -- Resolution: Won't Fix Fix Version/s: 0.14 There doesn't seem to be much community interest in supporting Ruby.NET. > Support for Ruby .NET Compiler > -- > > Key: NMAVEN-21 > URL: http://jira.codehaus.org/browse/NMAVEN-21 > Project: NMaven > Issue Type: New Feature > Environment: Windows, Linux, Mono, Microsoft >Reporter: Shane Isbell >Priority: Minor > Fix For: 0.14 > > > Add support for Ruby .NET compiler. This feature will use the Gardens Point > Ruby .NET compiler: http://plas.fit.qut.edu.au/Ruby.NET/ . -- 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-18) Archetype Plugins
[ http://jira.codehaus.org/browse/NMAVEN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-18. -- Resolution: Fixed Fix Version/s: 0.14 Fixed. > Archetype Plugins > - > > Key: NMAVEN-18 > URL: http://jira.codehaus.org/browse/NMAVEN-18 > Project: NMaven > Issue Type: New Feature >Reporter: Shane Isbell >Priority: Minor > Fix For: 0.14 > > > Archetype plugins that generate the directory structure and the pom.xml based > on target build environment: Visual Studio, SharpDevelop, CLI and on project > type: library, ASP.NET, etc. VS, SD and CLI may each have different directory > structures, but all projects, regardless of structure, will be buildable from > the command line. This extends the NMaven concept of making the build system > platform aware (in terms of compilers, vendors, OS) to also being build > structure aware (in terms of the dev environment). -- 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-16) Add NUnit Support to Visual Studio
[ http://jira.codehaus.org/browse/NMAVEN-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-16. -- Resolution: Fixed Fix Version/s: 0.14 NUnit support is already supported within the VS addin. > Add NUnit Support to Visual Studio > -- > > Key: NMAVEN-16 > URL: http://jira.codehaus.org/browse/NMAVEN-16 > Project: NMaven > Issue Type: New Feature > Environment: Windows, VS >Reporter: Shane Isbell >Priority: Minor > Fix For: 0.14 > > > Add support for NUnit to the Visual Studio IDE. I have not yet been able to > find an open-source (non-commercial) add-in that supports NUnit. There is > this project that just started: http://www.codeplex.com/VSUnit but it has not > released any source code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-50) "Invalid Header" in jar's Manifest (Specification-Title attribute) when tab char in pom Description
[
http://jira.codehaus.org/browse/MJAR-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116882
]
Mike Laurie commented on MJAR-50:
-
A tab can be a legal value in a manifest, but when the XML's formatting was
copied directly into the manifest, we ended up with a newline followed directly
by a tab, which is not valid for a manifest.
My suggestion to condense all whitespace was made purely because a manifest is
bound to be laid out differently from an XML description (which is likely to
have tab-based indents), so why not condense tabs while we're necessarily going
about removing newlines? Not strictly necessary though - you're right, as long
as continuation lines always start with a space (which they weren't)
> "Invalid Header" in jar's Manifest (Specification-Title attribute) when tab
> char in pom Description
> ---
>
> Key: MJAR-50
> URL: http://jira.codehaus.org/browse/MJAR-50
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Mike Laurie
>Priority: Trivial
>
> I typed a element into my pom; the description spanned 2 lines,
> and my text editor put a tab char at the beginning of the 2nd line.
> The project built correctly, but another project depended on the resulting
> jar.
> The compilation of the depending project failed with "invalid header" on the
> jar I'd just compiled.
> When I looked at the jar's manifest, I saw the Specification-Title attribute
> had the tab character still in it from the element.
> Replacing the tab with spaces in the pom solved the problem.
> However, this was valid xml that caused a compilation problem, so I think
> it's a minor bug with the jar production code.
> Note that the full description is trimmed before going into the manifest, so
> any
> Easy to work around, but it would be nice if whitespace in the
> element were consolidated into spaces before copying to the manifest.
> Doesn't need any fancy layout stuff - just any multiple instances of tabs,
> spaces, lf or cr should be replaced by a single space.
> Try (I haven't tried to compile this!):
> {code}
> public String consolidateWhitespace(String input){
> StringTokenizer st = new StringTokenizer(input);
> StringBuffer rv = new StringBuffer();
> while (st.hasMoreTokens()){
> rv.append(st.nextToken() + (st.hasMoreTokens()?" ":""));
> }
> return rv.toString();
> }
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MJAR-42) Add LICENCE and NOTICE files to the jar
[ http://jira.codehaus.org/browse/MJAR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MJAR-42. Resolution: Won't Fix This is now dealt with by the remote resources plugin. > Add LICENCE and NOTICE files to the jar > --- > > Key: MJAR-42 > URL: http://jira.codehaus.org/browse/MJAR-42 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Jeremy Boynes > Attachments: mvn-jar-patch.txt > > > Patch attached that adds project LICENSE and NOTICE files into the output > jar. By default it will add LICENSE.txt and NOTICE.txt files from the > project's basedir (if they are present) into the META-INF directory of the > jar. -- 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: (MJAR-50) "Invalid Header" in jar's Manifest (Specification-Title attribute) when tab char in pom Description
[
http://jira.codehaus.org/browse/MJAR-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116879
]
Olivier Lamy commented on MJAR-50:
--
If I correctly read sun specs.
{noformat}
newline: CR LF | LF | CR (not followed by LF)
value:SPACE *otherchar newline *continuation
continuation: SPACE *otherchar newline
otherchar:any UTF-8 character except NUL, CR and LF
{noformat}
I don't why tab can't be considered as legal value ?
> "Invalid Header" in jar's Manifest (Specification-Title attribute) when tab
> char in pom Description
> ---
>
> Key: MJAR-50
> URL: http://jira.codehaus.org/browse/MJAR-50
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Mike Laurie
>Priority: Trivial
>
> I typed a element into my pom; the description spanned 2 lines,
> and my text editor put a tab char at the beginning of the 2nd line.
> The project built correctly, but another project depended on the resulting
> jar.
> The compilation of the depending project failed with "invalid header" on the
> jar I'd just compiled.
> When I looked at the jar's manifest, I saw the Specification-Title attribute
> had the tab character still in it from the element.
> Replacing the tab with spaces in the pom solved the problem.
> However, this was valid xml that caused a compilation problem, so I think
> it's a minor bug with the jar production code.
> Note that the full description is trimmed before going into the manifest, so
> any
> Easy to work around, but it would be nice if whitespace in the
> element were consolidated into spaces before copying to the manifest.
> Doesn't need any fancy layout stuff - just any multiple instances of tabs,
> spaces, lf or cr should be replaced by a single space.
> Try (I haven't tried to compile this!):
> {code}
> public String consolidateWhitespace(String input){
> StringTokenizer st = new StringTokenizer(input);
> StringBuffer rv = new StringBuffer();
> while (st.hasMoreTokens()){
> rv.append(st.nextToken() + (st.hasMoreTokens()?" ":""));
> }
> return rv.toString();
> }
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MJAR-74) Upgrade maven-archiver dependency to 2.3-SNAPSHOT
[ http://jira.codehaus.org/browse/MJAR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MJAR-74: - Assignee: Olivier Lamy Affects Version/s: 2.0 2.1 Fix Version/s: 2.2 > Upgrade maven-archiver dependency to 2.3-SNAPSHOT > - > > Key: MJAR-74 > URL: http://jira.codehaus.org/browse/MJAR-74 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Affects Versions: 2.0, 2.1 >Reporter: Jochen Wiedmann >Assignee: Olivier Lamy > Fix For: 2.2 > > > Making use of MNG-2854 should increase the plugins performance. -- 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-2542) Remove carriage returns and tabs from field values in the manifest file
[
http://jira.codehaus.org/browse/MNG-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116878
]
Olivier Lamy commented on MNG-2542:
---
But If I correctly read
http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Name-Value%20pairs%20and%20Sections
I don't see why tab in value should be exclude.
section: *header +newline
nonempty-section: +header +newline
newline: CR LF | LF | CR (not followed by LF)
header: name : value
name: alphanum *headerchar
value: SPACE *otherchar newline *continuation
continuation: SPACE *otherchar newline
alphanum: {A-Z} | {a-z} | {0-9}
headerchar:alphanum | - | _
otherchar: any UTF-8 character except NUL, CR and LF
Concerning CR is related to PLX-185.
> Remove carriage returns and tabs from field values in the manifest file
> ---
>
> Key: MNG-2542
> URL: http://jira.codehaus.org/browse/MNG-2542
> Project: Maven 2
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: 2.0.4
>Reporter: Tim O'Brien
> Fix For: Shared Components
>
>
> When creating a JAR Manfiest, maven needs to remove CR and Tabs from the
> description taken from the POM.
> This is a critical issue with JAR files created from Maven. The issue is
> that Maven can create a MANIFEST file for a JAR, but it creates an invalid
> manifest if you jsut happen to have a description in your POM like thi:
>
> this is an library for idiots
>
> The issue is that your description element has new line characters and thejar
> plugin just take those new line characters and blindly copies them into the
> Manfiest, creating an invalid Manifest. This doesn't show up until you try
> to use the JAR in another application. Then you get a very cryptic error
> message about having an invalid jar.
> This used to be 1247 but it was closed and marked as Won't Fix with no
> explanation as to why it isn't worth fixing.
--
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-2542) Remove carriage returns and tabs from field values in the manifest file
[
http://jira.codehaus.org/browse/MNG-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116877
]
Olivier Lamy commented on MNG-2542:
---
Just tested with plexus-archiver-1.0-alpha-9 and current archiver trunk (rev
604294).
CR (line.separator) is fixed.
Tabs ('\u0009') is not fixed.
> Remove carriage returns and tabs from field values in the manifest file
> ---
>
> Key: MNG-2542
> URL: http://jira.codehaus.org/browse/MNG-2542
> Project: Maven 2
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: 2.0.4
>Reporter: Tim O'Brien
> Fix For: Shared Components
>
>
> When creating a JAR Manfiest, maven needs to remove CR and Tabs from the
> description taken from the POM.
> This is a critical issue with JAR files created from Maven. The issue is
> that Maven can create a MANIFEST file for a JAR, but it creates an invalid
> manifest if you jsut happen to have a description in your POM like thi:
>
> this is an library for idiots
>
> The issue is that your description element has new line characters and thejar
> plugin just take those new line characters and blindly copies them into the
> Manfiest, creating an invalid Manifest. This doesn't show up until you try
> to use the JAR in another application. Then you get a very cryptic error
> message about having an invalid jar.
> This used to be 1247 but it was closed and marked as Won't Fix with no
> explanation as to why it isn't worth fixing.
--
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-3322) Skip phase
Skip phase -- Key: MNG-3322 URL: http://jira.codehaus.org/browse/MNG-3322 Project: Maven 2 Issue Type: New Feature Components: Command Line Affects Versions: 2.0.8 Reporter: Paul Gier It would be helpful to be able to skip certain phases of execution. Similar to the way that the tests can be skipped with "maven.test.skip". I would like this to be generalized to skip any phase, so you could have something like: mvn -Dskip.phase=test-compile,process-test-classes,test All plugins in each of the phases in the comma separated list would be skipped during the build process. -- 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-2908) Make it possible to not generate Implementation-Version for MANIFEST.MF
[
http://jira.codehaus.org/browse/MNG-2908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MNG-2908.
-
Assignee: Olivier Lamy
Resolution: Fixed
Looks to be fixed.
But I have added a unit test for this in rev 604323.
> Make it possible to not generate Implementation-Version for MANIFEST.MF
> ---
>
> Key: MNG-2908
> URL: http://jira.codehaus.org/browse/MNG-2908
> Project: Maven 2
> Issue Type: Wish
> Components: maven-archiver
>Affects Versions: 2.0.5
>Reporter: Håvard Wigtil
>Assignee: Olivier Lamy
> Fix For: Reviewed Pending Version Assignment
>
>
> Maven puts "Implementation-Version: ${project.version}" in MANIFEST.MF when
> it creates an EAR file.
> This line is giving me some problems when I try to deploy the EAR on a BEA
> Weblogic application server, so I'd like for Maven not to generate this line.
> I didn't find any documented configuration setting for this, so I've looked
> in the source and found that there is a conditional checking for
> "addDefaultImplementationEntries" in
> https://svn.apache.org/repos/asf/maven/shared/tags/maven-archiver-2.2/src/main/java/org/apache/maven/archiver/ManifestConfiguration.java.
> When I try to set this setting from pom.xml with something like this, it
> fails:
> maven-ear-plugin
>
>
> false
>
>
> false
>
>
> Is it possible to skip Implementation-Version in the manifest, and in case,
> how?
--
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-3321) Skip plugin and/or execution
[
http://jira.codehaus.org/browse/MNG-3321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116875
]
Paul Gier commented on MNG-3321:
Additionally, maybe multiple plugins could be skipped by passing a comma
separated list. Like this:
mvn
-Dskip.plugins=org.apache.maven.plugins:maven-surefire-plugin,org.apache.maven.plugins:maven-jar-plugin
install
The same syntax could be applied to skipping individual executions.
> Skip plugin and/or execution
>
>
> Key: MNG-3321
> URL: http://jira.codehaus.org/browse/MNG-3321
> Project: Maven 2
> Issue Type: New Feature
> Components: Command Line
>Affects Versions: 2.0.8
>Reporter: Paul Gier
>
> Add ability to skip the execution of certain plugins. From the command line
> this could look something like:
> {code} mvn -Dskip.plugin:org.apache.maven.plugins:maven-surefire-plugin
> install {code}
> Also useful would be the ability to skip individual executions of a plugin.
> For example, if the surefire plugin had two executions defined as "ex1" and
> "ex2", you could do something like this:
> {code} mvn -Dskip.plugin:org.apache.maven.plugins:maven-surefire-plugin:ex1
> install {code}
> This would skip ex1 but still run ex2.
--
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-3321) Skip plugin and/or execution
Skip plugin and/or execution
Key: MNG-3321
URL: http://jira.codehaus.org/browse/MNG-3321
Project: Maven 2
Issue Type: New Feature
Components: Command Line
Affects Versions: 2.0.8
Reporter: Paul Gier
Add ability to skip the execution of certain plugins. From the command line
this could look something like:
{code} mvn -Dskip.plugin:org.apache.maven.plugins:maven-surefire-plugin install
{code}
Also useful would be the ability to skip individual executions of a plugin.
For example, if the surefire plugin had two executions defined as "ex1" and
"ex2", you could do something like this:
{code} mvn -Dskip.plugin:org.apache.maven.plugins:maven-surefire-plugin:ex1
install {code}
This would skip ex1 but still run ex2.
--
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-628) In the audit.log file the userid for each action is guest, even though the deploy was performed by admin
[ http://jira.codehaus.org/browse/MRM-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated MRM-628: Environment: Windows XP Archiva 1.0 was:Windows XP - Note I am running Maestro-1.5-M3 > In the audit.log file the userid for each action is guest, even though the > deploy was performed by admin > > > Key: MRM-628 > URL: http://jira.codehaus.org/browse/MRM-628 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0 > Environment: Windows XP > Archiva 1.0 >Reporter: Lisa Malgeri > > my settings.xml file has admin as the account in the section for > the repositories -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-628) In the audit.log file the userid for each action is guest, even though the deploy was performed by admin
In the audit.log file the userid for each action is guest, even though the deploy was performed by admin Key: MRM-628 URL: http://jira.codehaus.org/browse/MRM-628 Project: Archiva Issue Type: Bug Affects Versions: 1.0 Environment: Windows XP - Note I am running Maestro-1.5-M3 Reporter: Lisa Malgeri my settings.xml file has admin as the account in the section for the repositories -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-198) Support for images with links
Support for images with links -- Key: DOXIA-198 URL: http://jira.codehaus.org/browse/DOXIA-198 Project: Maven Doxia Issue Type: New Feature Affects Versions: 1.0-alpha-10 Reporter: Juan F. Codagnone Attachments: DOXIA-198-r24.diff Support for linked images. For example: [[http://twiki.org][http://twiki.org/logo.png]] in xhtml this is the same as http://twiki.org";>http://twiki.org/logo.png"/> Author: Juan F. Codagnone (for Zauber S.A.) Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ revision 24 -- 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: (DOXIA-197) more checkstyle issues
more checkstyle issues -- Key: DOXIA-197 URL: http://jira.codehaus.org/browse/DOXIA-197 Project: Maven Doxia Issue Type: Task Components: Module - Twiki Affects Versions: 1.0-alpha-10 Reporter: Juan F. Codagnone Priority: Trivial more checkstyle issues -- 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: (DOXIA-196) Support for block
Support for block Key: DOXIA-196 URL: http://jira.codehaus.org/browse/DOXIA-196 Project: Maven Doxia Issue Type: New Feature Components: Module - Twiki Affects Versions: 1.0-alpha-10 Reporter: Juan F. Codagnone Attachments: DOXIA-196-r22.diff Verbatim blocks initial support: some code... Author: Christian Nardi (for Zauber S.A.) Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ revision 22. -- 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: (DOXIA-195) Guess a title for the parsed page
[ http://jira.codehaus.org/browse/DOXIA-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan F. Codagnone updated DOXIA-195: Attachment: DOXIA-195-r21.diff missing testcase (revision 21 from https://code.zauber.com.ar/repos/doxia/branches/592499/ ) > Guess a title for the parsed page > - > > Key: DOXIA-195 > URL: http://jira.codehaus.org/browse/DOXIA-195 > Project: Maven Doxia > Issue Type: New Feature > Components: Module - Twiki >Reporter: Juan F. Codagnone > Attachments: DOXIA-195-r21.diff, DOXIA-195_r20.diff > > > TWikiParser now tries to guess the title for the page. It tries to use the > first section title it found. This allows maven sites that use twiki pages to > have a title in the pages. > Author: Juan F. Codagnone (for Zauber S.A.) > Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ > revision 20 -- 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: (DOXIA-195) Guess a title for the parsed page
Guess a title for the parsed page - Key: DOXIA-195 URL: http://jira.codehaus.org/browse/DOXIA-195 Project: Maven Doxia Issue Type: New Feature Components: Module - Twiki Reporter: Juan F. Codagnone Attachments: DOXIA-195-r21.diff, DOXIA-195_r20.diff TWikiParser now tries to guess the title for the page. It tries to use the first section title it found. This allows maven sites that use twiki pages to have a title in the pages. Author: Juan F. Codagnone (for Zauber S.A.) Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ revision 20 -- 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: (DOXIA-127) Twiki module cannot parse two forced links in the same paragraph
[ http://jira.codehaus.org/browse/DOXIA-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan F. Codagnone updated DOXIA-127: Attachment: DOXIA-127_r19.diff Author: Christian Nardi (for Zauber S.A.) Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ revision 19 > Twiki module cannot parse two forced links in the same paragraph > > > Key: DOXIA-127 > URL: http://jira.codehaus.org/browse/DOXIA-127 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Twiki >Affects Versions: 1.0-alpha-9 >Reporter: Dave Syer > Fix For: 1.0 > > Attachments: DOXIA-127_r19.diff > > > The regex used is too eager so it sucks up two (or more) links on the same > line, e.g. [[a]] b [[c]] parses as "[[" "a]] b [[c" "]]". THe fix is > relatively easy - just use a more specific regx to match for links (forced > and/or specifc). -- 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: (DOXIA-194) Generate usefull links for WikiWords
Generate usefull links for WikiWords Key: DOXIA-194 URL: http://jira.codehaus.org/browse/DOXIA-194 Project: Maven Doxia Issue Type: Improvement Components: Module - Twiki Reporter: Juan F. Codagnone Attachments: DOXIA-194_r18.diff [[WikiWord][text]] links used to generate links links like #WikiWord. This is not useful when the parser is used to generate a mvn-site site. With this patch there is a new entity called WikiWordLinkResolver that is responsible for resolving the href for the links. The default implementation is generates links to WikiWord.html that can be used to build a site. Author: Christian Nardi (for Zauber S.A.) Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ revision 18 -- 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-2768) Please update plexus-archiver dep to 1.0-alpha-8
[ http://jira.codehaus.org/browse/MNG-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MNG-2768. - Assignee: Olivier Lamy Resolution: Fixed done in rev 604307. Bumped plexus-archiver to 1.0-alpha-9 > Please update plexus-archiver dep to 1.0-alpha-8 > > > Key: MNG-2768 > URL: http://jira.codehaus.org/browse/MNG-2768 > Project: Maven 2 > Issue Type: Bug > Components: maven-archiver >Reporter: Max Bowsher >Assignee: Olivier Lamy > Fix For: Reviewed Pending Version Assignment > > > plexus-archiver 1.0-alpha-8 is released, containing, amongst other things, a > fix for PLX-234 aka PLXCOMP-10. -- 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: (DOXIA-193) forced url links where parsed as WikiWords links
forced url links where parsed as WikiWords links Key: DOXIA-193 URL: http://jira.codehaus.org/browse/DOXIA-193 Project: Maven Doxia Issue Type: Bug Components: Module - Twiki Affects Versions: 1.0-alpha-10 Reporter: Juan F. Codagnone Links like [[http://twiki.com]] were transformed to wikiwords links. Author: Christian Nardi (for Zauber S.A.) Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ revision 17 -- 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: (DOXIA-192) checkstyle
checkstyle -- Key: DOXIA-192 URL: http://jira.codehaus.org/browse/DOXIA-192 Project: Maven Doxia Issue Type: Improvement Affects Versions: 1.0-alpha-10 Reporter: Juan F. Codagnone Priority: Trivial Attachments: DOXIA-192_r15.diff, DOXIA-192_r16.diff some checkstyle fixes in two patches. Author: Christian Nardi (for Zauber S.A.) Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ revision 15 and 16. -- 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-72) Option to include source within the jar artifact
[
http://jira.codehaus.org/browse/MJAR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MJAR-72.
Assignee: Olivier Lamy
Resolution: Won't Fix
As explained, just add the resource in your pom :
{code:xml}
src/main/java
{code}
And the sources will be included in the jar.
> Option to include source within the jar artifact
>
>
> Key: MJAR-72
> URL: http://jira.codehaus.org/browse/MJAR-72
> Project: Maven 2.x Jar Plugin
> Issue Type: New Feature
> Environment: maven 2.0.6, jdk 1.6
>Reporter: Brill Pappin
>Assignee: Olivier Lamy
>
> I know it's fairly easy to create a separate source jar that contain the java
> source, but I've run across a case where I want to include the source along
> with the classes in the same jar.
> In this case the jars are GWT modules which use the source to compile the
> java code into javascript.
--
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: (DOXIA-191) Display images given an url
Display images given an url --- Key: DOXIA-191 URL: http://jira.codehaus.org/browse/DOXIA-191 Project: Maven Doxia Issue Type: Improvement Components: Module - Twiki Affects Versions: 1.0-alpha-10 Reporter: Juan F. Codagnone Attachments: DOXIA-191_r14.diff In the original release of the twiki parser, images weren't supported. Author: Christian Nardi (for Zauber S.A.) Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ revision 14. -- 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: (DOXIA-190) text like (=something=) is parsed incorrectly
text like (=something=) is parsed incorrectly - Key: DOXIA-190 URL: http://jira.codehaus.org/browse/DOXIA-190 Project: Maven Doxia Issue Type: Bug Components: Module - Twiki Affects Versions: 1.0-alpha-10 Reporter: Juan F. Codagnone Attachments: 13.diff Text like: (=something=) is parsed incorrectly Author: Christian Nardi Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ revision 13. -- 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: (MJAR-30) Allow includes/excludes specification
[ http://jira.codehaus.org/browse/MJAR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116861 ] Olivier Lamy commented on MJAR-30: -- IMHO this issue can be closed because it works in the trunk. Thoughts ? > Allow includes/excludes specification > - > > Key: MJAR-30 > URL: http://jira.codehaus.org/browse/MJAR-30 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Michael Böckling >Assignee: Mauro Talevi > Fix For: 2.2 > > Attachments: fail-patch.txt, maven-jar-plugin-2.2-SNAPSHOT.jar, > MJAR-30-maven-jar-plugin-1.patch, MJAR-30-maven-jar-plugin-renamed.patch > > > Allow the specification of includes / excludes to customise jar content. -- 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: (MRRESOURCES-30) When comparing organizations, don't compare the url
[ http://jira.codehaus.org/browse/MRRESOURCES-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116858 ] sebbaz+ch commented on MRRESOURCES-30: -- Or perhaps have a list of aliases for names and URLs? > When comparing organizations, don't compare the url > --- > > Key: MRRESOURCES-30 > URL: http://jira.codehaus.org/browse/MRRESOURCES-30 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-6, 1.0-beta-2 >Reporter: Dennis Lundberg > Attachments: NOTICE > > > The OrganizationComparator in ProcessRemoteResourcesMojo takes into account > both the organization's name *and* url. This leads to strange generated > NOTICE files, like the one attached, which comes from a slightly modified > trunk of commons-validator. I feel that the comparator should be changed so > that it only compares the name of the organization. An alternative way would > be to have two configurable comparators to choose from. I'm willing to do the > coding, but want to solicit other's opinions first. > Also see discussions here: > https://issues.apache.org/jira/browse/COMMONSSITE-21 -- 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-30) When comparing organizations, don't compare the url
When comparing organizations, don't compare the url --- Key: MRRESOURCES-30 URL: http://jira.codehaus.org/browse/MRRESOURCES-30 Project: Maven 2.x Remote Resources Plugin Issue Type: Bug Affects Versions: 1.0-beta-2, 1.0-alpha-6 Reporter: Dennis Lundberg Attachments: NOTICE The OrganizationComparator in ProcessRemoteResourcesMojo takes into account both the organization's name *and* url. This leads to strange generated NOTICE files, like the one attached, which comes from a slightly modified trunk of commons-validator. I feel that the comparator should be changed so that it only compares the name of the organization. An alternative way would be to have two configurable comparators to choose from. I'm willing to do the coding, but want to solicit other's opinions first. Also see discussions here: https://issues.apache.org/jira/browse/COMMONSSITE-21 -- 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: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report
[ http://jira.codehaus.org/browse/MCHANGES-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116843 ] Dennis Lundberg commented on MCHANGES-88: - Confirming this on Windows as well with maven-site-plugin 2.0-beta-6. > NoSuchMethodError with maven 2.0.8 when generating changes-report > - > > Key: MCHANGES-88 > URL: http://jira.codehaus.org/browse/MCHANGES-88 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: changes-report >Affects Versions: 2.0-beta-3 > Environment: [EMAIL PROTECTED]:/opt/nc/workspace/test_maven$ mvn > -version > Maven version: 2.0.8 > Java version: 1.6.0_03 > OS name: "linux" version: "2.6.18-5-686" arch: "i386" Family: "unix" >Reporter: Julien Graglia > Attachments: error.log, pom.xml > > > I create a simple maven2 project, but when i call > mvn -X -e changes:changes-report > I get an error (full log in attachment) > java.lang.NoSuchMethodError: > org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink; > at > org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:63) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) -- 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: (MANTRUN-79) Please upgrade to ant-1.7.0 from an-1.6.5
[ http://jira.codehaus.org/browse/MANTRUN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MANTRUN-79. -- Resolution: Duplicate > Please upgrade to ant-1.7.0 from an-1.6.5 > - > > Key: MANTRUN-79 > URL: http://jira.codehaus.org/browse/MANTRUN-79 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Reporter: Jason Chaffee > > We have to use ant-1.7.0 and ant-launcher-1.7.0 for some of things we do > because 1.6.5 does not have support. However, we have all types of > classloader issues because anrun has a dependency on 1.6.5 for these > artifacts. > 1.7.0 has been out for a long time and it is backwards compatible. It should > be an easy thing to fix for the next release...which hopefully won't be in > two years which seems like the current life cycle. -- 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: (MWAR-111) Transitive dependencies of optional dependencies are included in WEB-INF/lib
[ http://jira.codehaus.org/browse/MWAR-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Naas updated MWAR-111: Attachment: MWAR-111.patch Here is a patch that does a full search of the project dependencies instead of just one level deep. This is incredibly important for our company as we deploy ears, exclusively and if it scans through the entire dependency list to see if its optional, we can simply have one project control all of our common optional dependencies. > Transitive dependencies of optional dependencies are included in WEB-INF/lib > > > Key: MWAR-111 > URL: http://jira.codehaus.org/browse/MWAR-111 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: Maven 2.0.7, JDK 1.6.0_01-b06, JavaEE 5 >Reporter: Chris Lance > Attachments: AbstractWarMojo.java, MWAR-111.patch, TestProject.zip > > > I have an EAR project (TestEAR) which contains two modules: > 1. A JAR module (TestJAR) which has one dependency: commons-lang 2.3 > 2. A WAR module (TestWAR) which uses [these > instructions|http://maven.apache.org/plugins/maven-war-plugin/examples/war-manifest-guide.html] > to declare a dependency on TestJAR so that TestJAR is included in TestWAR's > manifest classpath, but not copied into WEB-INF/lib (i.e. declares the > dependency optional). > This works fine for TestJAR itself, but its transitive dependency > (commons-lang 2.3) is still copied into WEB-INF/lib. I don't believe this is > the correct behavior since all dependencies of a JAR packaged in the EAR must > also be packaged in the EAR. So, all a WAR should have to do is put the > transitive dependencies in its manifest classpath to inherit them. Basically: > in a WAR, transitive dependencies of "optional" dependencies should inherit > the "optional" flag. > I have included a simple test project as an example. Unzip, cd TestProject, > and mvn install. Look in TestEAR's target dir and you will see that > commons-lang is included in the EAR. Then look in TestWAR's target dir and > you will see that commons-lang is also included in both the manifest > classpath and the WEB-INF/lib dir. -- 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-37) eclipse:eclipse should execute in a later phase than "generate-sources"
[ http://jira.codehaus.org/browse/MECLIPSE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116831 ] nicolas de loof commented on MECLIPSE-37: - I searched a way to plug in the DefaultArtifactResolver to "register" the modules as artifacts and bypass dependency issues, but this is realy too complex for me... > eclipse:eclipse should execute in a later phase than "generate-sources" > --- > > Key: MECLIPSE-37 > URL: http://jira.codehaus.org/browse/MECLIPSE-37 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Dependencies resolution and build path >Affects Versions: 2.0 >Reporter: Mark Donszelmann >Assignee: fabrizio giustina > > the eclipse:eclipse goal should run in a later phase than it currently does > (generate-sources) > as user defined plugins may add to the compileSourceRoots and > testCompileSourceRoots. > If it runs later, added paths will be written correctly to the .classpath. > Suggested phase is "test" -- 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] Issue Comment Edited: (NMAVEN-99) Need a VB .NET quickstart archetype
[ http://jira.codehaus.org/browse/NMAVEN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116825 ] tcue edited comment on NMAVEN-99 at 12/14/07 9:50 AM: - Patch attached. Added a simple VB project that will have an executable output and print Hello World when executed. Also added a simple NUnit test case. Note that we need to comment out on nunit-console.exe.config for the tests to work. was (Author: tcue): Patch attached. Added a simple VB project that will have an executable output and print Hello World when executed. Also added a simple NUnit test case. > Need a VB .NET quickstart archetype > --- > > Key: NMAVEN-99 > URL: http://jira.codehaus.org/browse/NMAVEN-99 > Project: NMaven > Issue Type: New Feature >Reporter: Teodoro Cue Jr. >Assignee: Teodoro Cue Jr. > Attachments: NMAVEN-99.patch > > > We need an archetype to generate a "Hello World" project for VB .NET similar > to the dotnet-simple archetype for C#. -- 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-99) Need a VB .NET quickstart archetype
[ http://jira.codehaus.org/browse/NMAVEN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teodoro Cue Jr. updated NMAVEN-99: -- Attachment: NMAVEN-99.patch Patch attached. Added a simple VB project that will have an executable output and print Hello World when executed. Also added a simple NUnit test case. > Need a VB .NET quickstart archetype > --- > > Key: NMAVEN-99 > URL: http://jira.codehaus.org/browse/NMAVEN-99 > Project: NMaven > Issue Type: New Feature >Reporter: Teodoro Cue Jr. >Assignee: Teodoro Cue Jr. > Attachments: NMAVEN-99.patch > > > We need an archetype to generate a "Hello World" project for VB .NET similar > to the dotnet-simple archetype for C#. -- 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-37) eclipse:eclipse should execute in a later phase than "generate-sources"
[ http://jira.codehaus.org/browse/MECLIPSE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116824 ] nicolas de loof commented on MECLIPSE-37: - Simply moving the generate-* phases prior to compile doesn't fully solve issues with the eclipsePlugin. Any generate plugin that requires dependencyResolution (example : maven-ear-plugin) will require other project artifacts present in the local repo to create the eclipse configuration. In such case, there is no way to configure eclipse to fix a broken project. A complete fix would require a new early phase for plugins to DECLARE generated source folders. This would change the default lifecycle and requires many plugins updates. Another option could be that the reactor automagically registers modules as pseudo-artifacts and ignores them during dependency resolution. There would still be an issue with projects that have attached artifacts (example : test-jar) that may be set as dependencies on other modules. In such case the reactor should also ignore type and classifier... > eclipse:eclipse should execute in a later phase than "generate-sources" > --- > > Key: MECLIPSE-37 > URL: http://jira.codehaus.org/browse/MECLIPSE-37 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Dependencies resolution and build path >Affects Versions: 2.0 >Reporter: Mark Donszelmann >Assignee: fabrizio giustina > > the eclipse:eclipse goal should run in a later phase than it currently does > (generate-sources) > as user defined plugins may add to the compileSourceRoots and > testCompileSourceRoots. > If it runs later, added paths will be written correctly to the .classpath. > Suggested phase is "test" -- 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-627) Archiva doesn't download SNAPSHOTs for proxied repositories.
[ http://jira.codehaus.org/browse/MRM-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116823 ] gumnaam commented on MRM-627: - Found the problem. The culprit seems to be Maven 2.0.7+. It has problems with SNAPSHOT dependency resolution with mirrorOf set tp *. The solution is outlined here. http://www.jfrog.org/sites/artifactory/latest/maven.html I did as the post suggested and it worked. May be this should end up on the WIKI, or archiva proxy setup guide. > Archiva doesn't download SNAPSHOTs for proxied repositories. > > > Key: MRM-627 > URL: http://jira.codehaus.org/browse/MRM-627 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0 > Environment: Linux, JDK 1.5, >Reporter: gumnaam > > I have setup Archiva Managed Internal Repository as my whole and sole mirror > in my settings.xml. > The settings.xml does not contain any other repository information, just the > mirror entry . > The Archiva Manged Internal Repository is set to proxy 4/5 external > repositories, > One of which contains certain SNAPSHOTs that I have as dependencies. > The proxy connector for this repository has snapshot policy set to "always", > I also tried > "daily", "hourly". But the SNAPSHOT is never downloaded any my build fails. > The log file shows no special activity. > Also I am including the link to the thread on user-list > http://www.nabble.com/Proxying-SNAPSHOT-repositories-td14336170.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-252) Error trying to create an EAR project that contains one web module. It doesn't point to the local project, but only tries to find it in the local and remote repositori
[ http://jira.codehaus.org/browse/MECLIPSE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116821 ] nicolas de loof commented on MECLIPSE-252: -- In an ideal world, we could run mvn eclipse:eclipse on a fresh checkout without having to build the project. The requirement for @execute generate-resources to get all source-code generator declare generated folders makes this impossible. An ear project is an example, but any other project that requires dependency resolution on the generate-resources phase will also. Based on this, it is not possible (not simple) to fix a broken project in eclipse, as maven can't generate the required configuration ! > Error trying to create an EAR project that contains one web module. It > doesn't point to the local project, but only tries to find it in the local > and remote repositories. > -- > > Key: MECLIPSE-252 > URL: http://jira.codehaus.org/browse/MECLIPSE-252 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Dependencies resolution and build path >Affects Versions: 2.3 >Reporter: Daniel Alheiros > > I have one structure that defines 3 projects: > project1-jar > project2-war > project3-ear > project2-war is just a WAR that contains the project1-jar as a library > (WEB-INF/lib) > project3-ear is an EAR that contains project2-war as its only web module. > When I run mvn package it works perfectly and creates the EAR containing the > proper WAR file and the application.xml, so it works fine, but when I run mvn > eclipse:eclipse to generate the projects, the ear project is not generated > properly as it tries to find the war in the local and remote repository as > the piece of logging show bellow: > [INFO] Building project3-ear > [INFO]task-segment: [eclipse:eclipse] > [INFO] > > [INFO] Preparing eclipse:eclipse > Downloading: > http://mycompany.central-repository/repo/com/mycompany/project2-war/1.0-SNAPSHOT/project2-war-1.0-SNAPSHOT.war > [WARNING] Unable to get resource > 'mycompanygroupid:project2-war:war:1.0-SNAPSHOT' from repository > mycompany.central-repository (http://mycompany.central-repository/repo) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: > -- > 1) mycompanygroupid:project2-war:war:1.0-SNAPSHOT > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=mycompanygroupid > -DartifactId=project2-war \ > -Dversion=1.0-SNAPSHOT -Dpackaging=war -Dfile=/path/to/file > Path to dependency: > 1) mycompanygroupid:project3-ear:ear:1.0-SNAPSHOT > 2) mycompanygroupid:project2-war:war:1.0-SNAPSHOT > -- > 1 required artifact is missing. > for artifact: > mycompanygroupid:project3-ear:ear:1.0-SNAPSHOT > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > mycompany.central-repository (http://mycompany.central-repository/repo) > If I follow this instructions and install my WAR file to my local repository, > it then works and makes my EAR project, but I believe it shouldn't be > necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (NMAVEN-99) Need a VB .NET quickstart archetype
Need a VB .NET quickstart archetype --- Key: NMAVEN-99 URL: http://jira.codehaus.org/browse/NMAVEN-99 Project: NMaven Issue Type: New Feature Reporter: Teodoro Cue Jr. We need an archetype to generate a "Hello World" project for VB .NET similar to the dotnet-simple archetype for C#. -- 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-627) Archiva doesn't download SNAPSHOTs for proxied repositories.
Archiva doesn't download SNAPSHOTs for proxied repositories. Key: MRM-627 URL: http://jira.codehaus.org/browse/MRM-627 Project: Archiva Issue Type: Bug Components: remote proxy Affects Versions: 1.0 Environment: Linux, JDK 1.5, Reporter: gumnaam I have setup Archiva Managed Internal Repository as my whole and sole mirror in my settings.xml. The settings.xml does not contain any other repository information, just the mirror entry . The Archiva Manged Internal Repository is set to proxy 4/5 external repositories, One of which contains certain SNAPSHOTs that I have as dependencies. The proxy connector for this repository has snapshot policy set to "always", I also tried "daily", "hourly". But the SNAPSHOT is never downloaded any my build fails. The log file shows no special activity. Also I am including the link to the thread on user-list http://www.nabble.com/Proxying-SNAPSHOT-repositories-td14336170.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: (MRM-627) Archiva doesn't download SNAPSHOTs for proxied repositories.
[ http://jira.codehaus.org/browse/MRM-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116819 ] gumnaam commented on MRM-627: - btw, the repository with SNAPSHOT dependencies is http://www.wicketstuff.org/maven/repository/ And my dependency is org.wicketstuff.wicketstuff-scriptaculous ver 1.3-SNAPSHOT > Archiva doesn't download SNAPSHOTs for proxied repositories. > > > Key: MRM-627 > URL: http://jira.codehaus.org/browse/MRM-627 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0 > Environment: Linux, JDK 1.5, >Reporter: gumnaam > > I have setup Archiva Managed Internal Repository as my whole and sole mirror > in my settings.xml. > The settings.xml does not contain any other repository information, just the > mirror entry . > The Archiva Manged Internal Repository is set to proxy 4/5 external > repositories, > One of which contains certain SNAPSHOTs that I have as dependencies. > The proxy connector for this repository has snapshot policy set to "always", > I also tried > "daily", "hourly". But the SNAPSHOT is never downloaded any my build fails. > The log file shows no special activity. > Also I am including the link to the thread on user-list > http://www.nabble.com/Proxying-SNAPSHOT-repositories-td14336170.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] Issue Comment Edited: (MINVOKER-18) two executions of the same pom causes a prooblem with interpolated-pom.xml
[ http://jira.codehaus.org/browse/MINVOKER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116817 ] gerhard6 edited comment on MINVOKER-18 at 12/14/07 8:24 AM: - ... was (Author: gerhard6): One more note: my proposed solution works, but has a small drawback: In some cases (eg. by interrupting a running process,) it can leave the interpolation file in place, and the next and all subsequent invocations then fail. So one more improvement would be either to also add the "deleteOnExit" flag or to always delete an old file before creating a new one Gerhard. > two executions of the same pom causes a prooblem with interpolated-pom.xml > -- > > Key: MINVOKER-18 > URL: http://jira.codehaus.org/browse/MINVOKER-18 > Project: Maven 2.x Invoker Plugin > Issue Type: Bug >Affects Versions: 1.1 > Environment: latest 1.1-SNAPSHOT Version, maven-2.0.7 >Reporter: Gerhard Langs >Assignee: Olivier Lamy > Fix For: 1.1 > > Attachments: invoker-18.patch, invoker-18.patch, > pom-interpolation2-invoked.xml, pom-interpolation2.xml > > > TestCase: >pom-interpolated2.xml uses invoker to invoke > "pom-interpolated2-invoked.xml in 2 "executions". > invocation: >mvn -f pom-interpolated2.xml test -e > the second execution fails, because it is unable to create the > "interpolated-pom.xml". > Proposed solution: >- dont tag the interpolated-pom.xml as "deleteOnExit", >- delete that file at the end of every execution. > Will try to provide a patch > Greetings, Gerhard > Output: > ... > Caused by: org.apache.maven.plugin.MojoExecutionException: fail to create > file > D:\maven\maven-invoker-plugin\src\test\resources\unit\interpolation2\.\interpolated-pom.xml > at > org.apache.maven.plugin.invoker.InvokerMojo.buildInterpolatedPomFile(InvokerMojo.java:997) > at > org.apache.maven.plugin.invoker.InvokerMojo.runBuild(InvokerMojo.java:458) > at > org.apache.maven.plugin.invoker.InvokerMojo.execute(InvokerMojo.java:341) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) -- 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: (MINVOKER-18) two executions of the same pom causes a prooblem with interpolated-pom.xml
[ http://jira.codehaus.org/browse/MINVOKER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116816 ] Gerhard Langs commented on MINVOKER-18: --- One more note: my proposed solution works, but has a small drawback: In some cases (eg. by interrupting a running process,) it can leave the interpolation file in place, and the next and all subsequent invocations then fail. So one more improvement would be either to also add the "deleteOnExit" flag or to always delete an old file before creating a new one Gerhard. > two executions of the same pom causes a prooblem with interpolated-pom.xml > -- > > Key: MINVOKER-18 > URL: http://jira.codehaus.org/browse/MINVOKER-18 > Project: Maven 2.x Invoker Plugin > Issue Type: Bug >Affects Versions: 1.1 > Environment: latest 1.1-SNAPSHOT Version, maven-2.0.7 >Reporter: Gerhard Langs >Assignee: Olivier Lamy > Fix For: 1.1 > > Attachments: invoker-18.patch, invoker-18.patch, > pom-interpolation2-invoked.xml, pom-interpolation2.xml > > > TestCase: >pom-interpolated2.xml uses invoker to invoke > "pom-interpolated2-invoked.xml in 2 "executions". > invocation: >mvn -f pom-interpolated2.xml test -e > the second execution fails, because it is unable to create the > "interpolated-pom.xml". > Proposed solution: >- dont tag the interpolated-pom.xml as "deleteOnExit", >- delete that file at the end of every execution. > Will try to provide a patch > Greetings, Gerhard > Output: > ... > Caused by: org.apache.maven.plugin.MojoExecutionException: fail to create > file > D:\maven\maven-invoker-plugin\src\test\resources\unit\interpolation2\.\interpolated-pom.xml > at > org.apache.maven.plugin.invoker.InvokerMojo.buildInterpolatedPomFile(InvokerMojo.java:997) > at > org.apache.maven.plugin.invoker.InvokerMojo.runBuild(InvokerMojo.java:458) > at > org.apache.maven.plugin.invoker.InvokerMojo.execute(InvokerMojo.java:341) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) -- 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: (MINVOKER-18) two executions of the same pom causes a prooblem with interpolated-pom.xml
[ http://jira.codehaus.org/browse/MINVOKER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116817 ] Gerhard Langs commented on MINVOKER-18: --- One more note: my proposed solution works, but has a small drawback: In some cases (eg. by interrupting a running process,) it can leave the interpolation file in place, and the next and all subsequent invocations then fail. So one more improvement would be either to also add the "deleteOnExit" flag or to always delete an old file before creating a new one Gerhard. > two executions of the same pom causes a prooblem with interpolated-pom.xml > -- > > Key: MINVOKER-18 > URL: http://jira.codehaus.org/browse/MINVOKER-18 > Project: Maven 2.x Invoker Plugin > Issue Type: Bug >Affects Versions: 1.1 > Environment: latest 1.1-SNAPSHOT Version, maven-2.0.7 >Reporter: Gerhard Langs >Assignee: Olivier Lamy > Fix For: 1.1 > > Attachments: invoker-18.patch, invoker-18.patch, > pom-interpolation2-invoked.xml, pom-interpolation2.xml > > > TestCase: >pom-interpolated2.xml uses invoker to invoke > "pom-interpolated2-invoked.xml in 2 "executions". > invocation: >mvn -f pom-interpolated2.xml test -e > the second execution fails, because it is unable to create the > "interpolated-pom.xml". > Proposed solution: >- dont tag the interpolated-pom.xml as "deleteOnExit", >- delete that file at the end of every execution. > Will try to provide a patch > Greetings, Gerhard > Output: > ... > Caused by: org.apache.maven.plugin.MojoExecutionException: fail to create > file > D:\maven\maven-invoker-plugin\src\test\resources\unit\interpolation2\.\interpolated-pom.xml > at > org.apache.maven.plugin.invoker.InvokerMojo.buildInterpolatedPomFile(InvokerMojo.java:997) > at > org.apache.maven.plugin.invoker.InvokerMojo.runBuild(InvokerMojo.java:458) > at > org.apache.maven.plugin.invoker.InvokerMojo.execute(InvokerMojo.java:341) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) -- 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-1602) UTF-8 characters imported from POM aren't properly stored/displayed
[
http://jira.codehaus.org/browse/CONTINUUM-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116814
]
Christian Mouttet commented on CONTINUUM-1602:
--
I noticed that character encoding isn't handled correct by the whole
application. If a caracter >7bit is filled in a text field (e. g. User
Edit/Full Name) a question mark is saved instead of the original input to
database (postgres in my case).
I tried this:
- going to "[Admin] Edit User"
- changing the character encoding in my Firefox bowser to UTF-8
- change Full Name (appending a non ASCII character e. g. 'ä')
- clicking "Update"
Result:
The List of Users shows exactly what I typed into the form.
If I don't change the character encoding (ISO-8859-1 is set by default) than
the question mark will be shown.
Remark:
Our Continuum server is running on SLES-9 with UTF-8 encoding.
> UTF-8 characters imported from POM aren't properly stored/displayed
> ---
>
> Key: CONTINUUM-1602
> URL: http://jira.codehaus.org/browse/CONTINUUM-1602
> Project: Continuum
> Issue Type: Bug
>Affects Versions: 1.1
> Environment: Linux (Fedora 8), locale UTF-8, Tomcat and Jetty,
> Firefox 2.0.0.10
>Reporter: Marcin Zajaczkowski
>Priority: Minor
> Attachments: pom.xml
>
>
> UTF-8 characters in imported POM file (tested with adding Maven2 project)
> aren't properly stored (or at least displayed).
> How to reproduce:
> 1. Import attached POM.
> 2. Check developers for added project
> 3. There is '?' in developer name ("F?falski") instead of proper UTF-8
> encoded Polish character 'ą' ("Fąfalski").
> Note:
> Character encoding for Continuum pages is setting by default to ISO-8859-1
> (which could be changed to UTF-8), but already in page source there is '?'
> character (so maybe it's wrongly stored in a database? - here using default
> Derby).
--
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-1854) please upload cobol2j to central repo
please upload cobol2j to central repo - Key: MAVENUPLOAD-1854 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1854 Project: maven-upload-requests Issue Type: Task Reporter: Pawel Maczka Please upload! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-268) Aggragated surefire report from modules
[ http://jira.codehaus.org/browse/SUREFIRE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116794 ] Amit commented on SUREFIRE-268: --- Hi, I would like to use this option. Can you advise me on how to implement this? I am using maven-surefire-plugin to test the code. > Aggragated surefire report from modules > --- > > Key: SUREFIRE-268 > URL: http://jira.codehaus.org/browse/SUREFIRE-268 > Project: Maven Surefire > Issue Type: New Feature > Components: report plugin >Affects Versions: 2.0 Report Plugin > Environment: all >Reporter: Bugittaa Pahasti > Fix For: 2.4 > > Attachments: patch.patch, patch2.patch, report.JPG > > > Aggregated surefire report from child modules. I think this has been > discussed in the mailing lists, but seemed not to be on Jira yet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-409) Upgrading to surefire 2.4-SNAPSHOT breaks my build
[ http://jira.codehaus.org/browse/SUREFIRE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116783 ] Jerome Lacoste commented on SUREFIRE-409: - sorry for the bad title. I can't change it. Better one: "test fails (due to bad plexus isolation?) after upgrading from 2.3 to latest 2.4 SNAPSHOT" > Upgrading to surefire 2.4-SNAPSHOT breaks my build > -- > > Key: SUREFIRE-409 > URL: http://jira.codehaus.org/browse/SUREFIRE-409 > Project: Maven Surefire > Issue Type: Bug > Components: classloading >Affects Versions: 2.4 >Reporter: Jerome Lacoste > Attachments: mvn_2.3_with_systemClassLoader.log, > mvn_2.3_without_systemClassLoader.log, mvn_2.4_with_systemClassLoader.log, > mvn_2.4_without_systemClassLoader.log, pom.diff, > pom_2.4_with_systemClassLoader.xml, svn_info.txt, test-failure-2.4.txt > > > If I upgrade surefire in the Mowebstart plugin project, I get test failures: > Caused by: java.lang.NoSuchMethodError: > org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties; > at > org.apache.maven.project.interpolation.RegexBasedModelInterpolator.(RegexBasedModelInterpolator.java:63 > ) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:494) > at java.lang.Class.newInstance0(Class.java:350) > at java.lang.Class.newInstance(Class.java:303) > at > org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44) > ... 43 more > It sounds like SUREFIRE-347. > Note that my build was broke on Windows. I usually build on Linux so I didn't > notice the problem. Maybe it has been there for a while. I also attach here > the error I was getting when building with 2.3 on Windows. So I removed the > useSystemClassLoader config (that was introduced to work-around SUREFIRE-347 > w/ surefire 2.3...) in my POM and the build passed again on Windows (didn't > try on Linux). > Then I upgraded to surefire plugin 2.4 and started to see failures in test. I > added the useSystemClassLoader=true section in the surefire plugin config > still the same issue. > I will try on linux when I get the 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] Updated: (SUREFIRE-409) Upgrading to surefire 2.4-SNAPSHOT breaks my build
[ http://jira.codehaus.org/browse/SUREFIRE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerome Lacoste updated SUREFIRE-409: Attachment: test-failure-2.4.txt svn_info.txt > Upgrading to surefire 2.4-SNAPSHOT breaks my build > -- > > Key: SUREFIRE-409 > URL: http://jira.codehaus.org/browse/SUREFIRE-409 > Project: Maven Surefire > Issue Type: Bug > Components: classloading >Affects Versions: 2.4 >Reporter: Jerome Lacoste > Attachments: mvn_2.3_with_systemClassLoader.log, > mvn_2.3_without_systemClassLoader.log, mvn_2.4_with_systemClassLoader.log, > mvn_2.4_without_systemClassLoader.log, pom.diff, > pom_2.4_with_systemClassLoader.xml, svn_info.txt, test-failure-2.4.txt > > > If I upgrade surefire in the Mowebstart plugin project, I get test failures: > Caused by: java.lang.NoSuchMethodError: > org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties; > at > org.apache.maven.project.interpolation.RegexBasedModelInterpolator.(RegexBasedModelInterpolator.java:63 > ) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:494) > at java.lang.Class.newInstance0(Class.java:350) > at java.lang.Class.newInstance(Class.java:303) > at > org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44) > ... 43 more > It sounds like SUREFIRE-347. > Note that my build was broke on Windows. I usually build on Linux so I didn't > notice the problem. Maybe it has been there for a while. I also attach here > the error I was getting when building with 2.3 on Windows. So I removed the > useSystemClassLoader config (that was introduced to work-around SUREFIRE-347 > w/ surefire 2.3...) in my POM and the build passed again on Windows (didn't > try on Linux). > Then I upgraded to surefire plugin 2.4 and started to see failures in test. I > added the useSystemClassLoader=true section in the surefire plugin config > still the same issue. > I will try on linux when I get the 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: (SUREFIRE-409) Upgrading to surefire 2.4-SNAPSHOT breaks my build
Upgrading to surefire 2.4-SNAPSHOT breaks my build -- Key: SUREFIRE-409 URL: http://jira.codehaus.org/browse/SUREFIRE-409 Project: Maven Surefire Issue Type: Bug Components: classloading Affects Versions: 2.4 Reporter: Jerome Lacoste Attachments: mvn_2.3_with_systemClassLoader.log, mvn_2.3_without_systemClassLoader.log, mvn_2.4_with_systemClassLoader.log, mvn_2.4_without_systemClassLoader.log, pom.diff, pom_2.4_with_systemClassLoader.xml, svn_info.txt, test-failure-2.4.txt If I upgrade surefire in the Mowebstart plugin project, I get test failures: Caused by: java.lang.NoSuchMethodError: org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties; at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.(RegexBasedModelInterpolator.java:63 ) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at java.lang.Class.newInstance0(Class.java:350) at java.lang.Class.newInstance(Class.java:303) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44) ... 43 more It sounds like SUREFIRE-347. Note that my build was broke on Windows. I usually build on Linux so I didn't notice the problem. Maybe it has been there for a while. I also attach here the error I was getting when building with 2.3 on Windows. So I removed the useSystemClassLoader config (that was introduced to work-around SUREFIRE-347 w/ surefire 2.3...) in my POM and the build passed again on Windows (didn't try on Linux). Then I upgraded to surefire plugin 2.4 and started to see failures in test. I added the useSystemClassLoader=true section in the surefire plugin config still the same issue. I will try on linux when I get the 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] Updated: (SUREFIRE-409) Upgrading to surefire 2.4-SNAPSHOT breaks my build
[ http://jira.codehaus.org/browse/SUREFIRE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerome Lacoste updated SUREFIRE-409: Attachment: pom_2.4_with_systemClassLoader.xml pom.diff mvn_2.4_without_systemClassLoader.log > Upgrading to surefire 2.4-SNAPSHOT breaks my build > -- > > Key: SUREFIRE-409 > URL: http://jira.codehaus.org/browse/SUREFIRE-409 > Project: Maven Surefire > Issue Type: Bug > Components: classloading >Affects Versions: 2.4 >Reporter: Jerome Lacoste > Attachments: mvn_2.3_with_systemClassLoader.log, > mvn_2.3_without_systemClassLoader.log, mvn_2.4_with_systemClassLoader.log, > mvn_2.4_without_systemClassLoader.log, pom.diff, > pom_2.4_with_systemClassLoader.xml, svn_info.txt, test-failure-2.4.txt > > > If I upgrade surefire in the Mowebstart plugin project, I get test failures: > Caused by: java.lang.NoSuchMethodError: > org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties; > at > org.apache.maven.project.interpolation.RegexBasedModelInterpolator.(RegexBasedModelInterpolator.java:63 > ) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:494) > at java.lang.Class.newInstance0(Class.java:350) > at java.lang.Class.newInstance(Class.java:303) > at > org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44) > ... 43 more > It sounds like SUREFIRE-347. > Note that my build was broke on Windows. I usually build on Linux so I didn't > notice the problem. Maybe it has been there for a while. I also attach here > the error I was getting when building with 2.3 on Windows. So I removed the > useSystemClassLoader config (that was introduced to work-around SUREFIRE-347 > w/ surefire 2.3...) in my POM and the build passed again on Windows (didn't > try on Linux). > Then I upgraded to surefire plugin 2.4 and started to see failures in test. I > added the useSystemClassLoader=true section in the surefire plugin config > still the same issue. > I will try on linux when I get the 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
