[jira] (ARCHETYPE-246) Poor Formatting # chains

2013-03-20 Thread Simon Goodall (JIRA) 

[ 
https://jira.codehaus.org/browse/ARCHETYPE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=36#comment-36
 ] 

Simon Goodall commented on ARCHETYPE-246:
-

I've just spent a few hours scratching my head for the same reason. Eclipse 
auto generates javadoc for bundle Activators with a #stop in the comment.

 Poor Formatting # chains
 

 Key: ARCHETYPE-246
 URL: https://jira.codehaus.org/browse/ARCHETYPE-246
 Project: Maven Archetype
  Issue Type: Bug
  Components: Creator
Affects Versions: 2.0-alpha-4
 Environment: GNU/Linux, Maven 2.1.0
Reporter: Libor Tvrdík
 Attachments: wrapper.conf


 All resources are formatted using Velocity. This is about right (even if the 
 parameter resource format=true/false would be good). The problem occurs 
 when I set the sources of the *#* character.
 In [Velocity user guide - 
 Escaping|http://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#escaping_vtl_directives]
  says that it is possible to use *\#*. But after run mvn archetype:create 
 still getting:
 {code}
 [DEBUG] * Debug info for resources created from generated 
 Model *** 
   
 [DEBUG] Was build element found in generated POM?: true   
   
   
 [INFO] * End of debug info from resources from generated 
 POM ***   

 [ERROR] ResourceManager.getResource() parse exception: 
 org.apache.velocity.exception.ParseErrorException: 
 Lexical error: org.apache.velocity.runtime.parser.TokenMgrError: Lexical 
 error at line 101, column 0.  Encountered: EOF after :
   
  
 [INFO] 
   
   

 [ERROR] BUILD ERROR   
   
   
 [INFO] 
   
   

 [INFO] Error creating from archetype  
   
   
 Embedded error: Error merging velocity templates
 Lexical error: org.apache.velocity.runtime.parser.TokenMgrError: Lexical 
 error at line 101, column 0.  Encountered: EOF after : 
 [INFO] 
   

 [DEBUG] Trace 
   
 org.apache.maven.lifecycle.LifecycleExecutionException: Error creating from 
 archetype   
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
   
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
  
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)

 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
   
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)

 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)

 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) 
   
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)   
   
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)  
   
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 

 at

[jira] Created: (MNG-4923) java.lang.ClassNotFoundException: org.apache.maven.artifact.ArtifactStatus

2010-12-03 Thread Simon Goodall (JIRA) 
java.lang.ClassNotFoundException: org.apache.maven.artifact.ArtifactStatus
--

 Key: MNG-4923
 URL: http://jira.codehaus.org/browse/MNG-4923
 Project: Maven 2  3
  Issue Type: Bug
Affects Versions: 3.0.1, 3.0
 Environment: Fedora 14, 64bit
JDK 1.6.0_22
Reporter: Simon Goodall
 Attachments: import-bundle-error.log

When attempting to run pax:import-bundle I get the following exception;

java.lang.ClassNotFoundException: org.apache.maven.artifact.ArtifactStatus

I only get this in maven 3, maven 2.2.1 works as expected.

To reproduce, I followed the example in 
http://www.sonatype.com/books/mhandbook-stage/reference/sect-osgi-generate-project.html

Namely;

1) mvn org.ops4j:maven-pax-plugin:create-project   
-DgroupId=org.sonatype.mcookbook   -DartifactId=osgi-project   
-Dversion=1.0-SNAPSHOT
2) cd osgi-project

3) mvn pax:import-bundle -DgroupId=org.apache.felix 
-DartifactId=org.apache.felix.webconsole-Dversion=1.2.8 


Step three fails. See attached for the output when run with -X


I would expect maven 3 to handle this as I understand it is meant to be 
backwards compatible with all maven 2 plugins.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MASSEMBLY-120) ModuleSet/Binaries include/exclude not implemented

2006-08-24 Thread Simon Goodall (JIRA) 
[ http://jira.codehaus.org/browse/MASSEMBLY-120?page=comments#action_73224 
] 

Simon Goodall commented on MASSEMBLY-120:
-

The fix is in the current snapshot version.

 ModuleSet/Binaries include/exclude not implemented
 --

 Key: MASSEMBLY-120
 URL: http://jira.codehaus.org/browse/MASSEMBLY-120
 Project: Maven 2.x Assembly Plugin
  Issue Type: Bug
Affects Versions: 2.1
 Environment: linux (fedora core 5) / maven 2.0.4 / java 1.5
Reporter: Simon Goodall
 Assigned To: John Casey

 The binaries section of moduleSet has an include / exclude section defined, 
 but it is not implemented. Currently a module can only include all or none of 
 its dependencies (through the includeDependencies tag). There is no selective 
 inclusion/exclusion of dependencies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MASSEMBLY-104) fileMode doesn't work with Cygwin

2006-06-22 Thread Simon Goodall (JIRA) 
[ http://jira.codehaus.org/browse/MASSEMBLY-104?page=comments#action_67928 
] 

Simon Goodall commented on MASSEMBLY-104:
-

The problem is a bug in the number parsing.
The processFileList method in AbstractAssemblyMojo.java has the following line;

archiver.addFile( source, outputDirectory + / + destName,
  Integer.parseInt( fileItem.getFileMode() ) );

which should read;

archiver.addFile( source, outputDirectory + / + destName,
  Integer.parseInt( fileItem.getFileMode(), 8 ) 
);


 fileMode doesn't work with Cygwin
 -

  Key: MASSEMBLY-104
  URL: http://jira.codehaus.org/browse/MASSEMBLY-104
  Project: Maven 2.x Assembly Plugin
 Type: Bug

 Versions: 2.1
  Environment: Windows 2002 XP Pro running Cygwin
 Reporter: Mark Heinze



 The fileMode does not correctly set the permissions on the file. This happens 
 in the filesfile/file/files tag in the asssembly XML file. Any files 
 copied with this tag ends up with strange permissions (including those with 
 the default fileMode).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Created: (MASSEMBLY-120) ModuleSet/Binaries include/exclude not implemented

2006-06-21 Thread Simon Goodall (JIRA) 
ModuleSet/Binaries include/exclude not implemented
--

 Key: MASSEMBLY-120
 URL: http://jira.codehaus.org/browse/MASSEMBLY-120
 Project: Maven 2.x Assembly Plugin
Type: Bug

Versions: 2.1
 Environment: linux (fedora core 5) / maven 2.0.4 / java 1.5
Reporter: Simon Goodall


The binaries section of moduleSet has an include / exclude section defined, but 
it is not implemented. Currently a module can only include all or none of its 
dependencies (through the includeDependencies tag). There is no selective 
inclusion/exclusion of dependencies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira