Re: Is ArchetypeProvider in mavenide/nb6.0 public api?
Srinivasan Chikkala Open ESB Community (http://open-esb.org) mkleint wrote: Srinivasan Chikkala wrote: Hi Milos, In order to make org.codehaus.mevenide.netbeans.api.**/* as public api in netbeans, you need to declare them in the module manifest file using some netbeans specific manifest entries. The current module is missing those entries and hence netbeans can not share these apis between modules unless you define a implementation dependency on this module which gives access to all classes in the module and using the implementation dependency is not the correct way to access apis between the nb modules. Well, that's not entirely true. You are encouraged to mark the public packages in the manifest, however if you don't, then all packages in that module are considered public. You get a warning in the log file though :) I'm referencing this module from all my other modules using the specification dependency, not implementation dependency and it works fine. You may be fine with using specification version during compile time as you are using a different tool (nbm maven plugin) which may be working differently from the IDE build harness , but I was surprised to hear that the runtime (ide) is not restricting it without the implementation dependency <http://wiki.netbeans.org/DevFaqImplementationDependency> ? Are you sure that maven plugin is not adding this implementation dependency automatically in your other modules? Is the IDE itself prohibiting access to adding a specification dependency at design time? (I wouldn't know as I'm using maven and maven projects support to build mevenide, not the default ant-based project type for developing netbeans modules) Yes. the IDE is not able to resolve the apis (you get errors in editor as well as at compilation) if I just define a specification dependency as these packages are not defines public. When I selected the implementation dependency every thing works. I guess I can still put an entry in the manifest that makes all packages public. What version do to need that to appear? 3.0.11 (which I plan to release at 6.1 M2 times) or is subversion trunk with 3.1 version (release date not specified yet) ok? I suppose the former, right? I don't recommend adding every package in the module to be public, but your are the one who known better about what in this package is useful to other modules, so it is up to you. Yes. It would be nice to have the public apis defined in the version that works with IDE 6.0 or 6.1 which I guess is the 3.0.11 Milos Please add these packages as module public apis in the module manifest file. regards, Srinivasan Chikkala Open ESB Community (http://open-esb.org) mkleint wrote: Srinivasan Chikkala wrote: I am trying to add list of archetypes to the maven ide new project wizard ( New Project -> Maven-> Maven Project [Maven Archetypes] ) from my netbeans module, but the api org.codehaus.mevenide.netbeans.api.archetype.ArchetypeProvider is not a public api to include it in my module dependency. When is this api becomes public? Is there any other way I can add my archetype info to the new project? like adding that info in the layer.xml etc. regards, As far as I'm concerned it's public api and i'm trying to keep the classes in api.* packages backward compatible. Are you having problems developing against the module? Regards Milos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is ArchetypeProvider in mavenide/nb6.0 public api?
Hi Milos, In order to make org.codehaus.mevenide.netbeans.api.**/* as public api in netbeans, you need to declare them in the module manifest file using some netbeans specific manifest entries. The current module is missing those entries and hence netbeans can not share these apis between modules unless you define a implementation dependency on this module which gives access to all classes in the module and using the implementation dependency is not the correct way to access apis between the nb modules. Please add these packages as module public apis in the module manifest file. regards, Srinivasan Chikkala Open ESB Community (http://open-esb.org) mkleint wrote: Srinivasan Chikkala wrote: I am trying to add list of archetypes to the maven ide new project wizard ( New Project -> Maven-> Maven Project [Maven Archetypes] ) from my netbeans module, but the api org.codehaus.mevenide.netbeans.api.archetype.ArchetypeProvider is not a public api to include it in my module dependency. When is this api becomes public? Is there any other way I can add my archetype info to the new project? like adding that info in the layer.xml etc. regards, As far as I'm concerned it's public api and i'm trying to keep the classes in api.* packages backward compatible. Are you having problems developing against the module? Regards Milos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Is ArchetypeProvider in mavenide/nb6.0 public api?
I am trying to add list of archetypes to the maven ide new project wizard ( New Project -> Maven-> Maven Project [Maven Archetypes] ) from my netbeans module, but the api org.codehaus.mevenide.netbeans.api.archetype.ArchetypeProvider is not a public api to include it in my module dependency. When is this api becomes public? Is there any other way I can add my archetype info to the new project? like adding that info in the layer.xml etc. regards, -- Srinivasan Chikkala Open ESB Community (http://open-esb.org) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
can I use deploy maven ant task to just deploy a jar and not it's pom?
I want to use maven ant tasks (2.0.7) to deploy a third party jar file to some repository. The command line "mvn deploy:deploy-file" has a facility to deploy the jar file alone without generating the pom in the repository. Is there a way to do that using deploy maven ant task? the above ant script deploys the xyz.jar as well as pom.xml to the repository. The pom.xml file passed is just to describe the group, artifact and version info. I don't want to populate this pom.xml in the repository. Is there a way to pass the group, artifact and version info of the jar file to the deploy task without using pom.xml? thanks, -- Srinivasan Chikkala Open ESB Community (http://open-esb.org) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How can I configure ant run plugin to run ant script with javac ant task with fork=false?
Hi
I am trying to call javac ant task in an ant script from ant run plugin
and getting the following error when the "fork" attribute is false in
the javac task in my ant script. The workaround is to set "fork" to
true, but how can I configure the ant run plugin so that it works with
the javac ant task in the ant script with "fork=false"
Error output
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [antrun:run {execution: my-compile}]
[INFO] Executing tasks
compile:
[echo] env.JAVA_HOME d:/Java/jdk1.5.0_06
[javac] Compiling 10 source files to
D:\chikkala\dev\mvn-plugin\MyBC2\build\classes
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: The following error occurred while executing this line:
D:\chikkala\dev\mvn-plugin\MyBC2\build.xml:97: Unable to find a javac
compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK
Here is my maven-antrun-plugin configuration
-
maven-antrun-plugin
my-compile-id
compile
run
inheritAll="false" target="compile" >
Here is the ant script in the build.xml
--
debug="flase" deprecation="false" source="1.5" target="1.5"
includeantruntime="false">
thanks,
--
Srinivasan Chikkala
Open ESB Community (http://open-esb.org)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: error getting maven-ant-plugin 2.0-SNAPSHOT
thanks, it works that way. You need to specify everything to work. Previously I did try using "mvn ant:2.0-beta-2-SNAPSHOT:ant" (partial-artifact-id:version:goal) thinking that it would determine the groupId and artifactId somehow if they are missing or partially specified from the command much like when you just do "mvn ant:ant" that is getting the latest plugin in the central repo, but it did not work and made me think there is no other way from command line. regards, Srinivasan Chikkala Open ESB Community (http://open-esb.org) Wayne Fay wrote: Yes, that is exactly correct: mvn groupId:artifactId:version:goal Wayne On 8/30/07, Srinivasan Chikkala <[EMAIL PROTECTED]> wrote: Thanks for the info. I fixed this part by removing the apache maven repository from the mirror and adding it as a repository ( I just copied the apache profile specified at http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html ) to my settings.xml. However, when I run "mvn ant:ant" it still picking up the "2.0-beta-1" from the central repository. So, I added the plugin configuration ( under ) explicitly in my project pom file to pick up the "2.0-beta-1-SNAPSHOT" and it downloaded and used that version, but got the exception using it. Another question is that if I don't want to configured the plugin in the project pom for a particular version of a plugin, what are my other options? Is the plugin registry the only option to force the mvn to use particular version of the plugin? how can I tell maven to use a particular version of the plugin using command line options when I am calling the plugin goal directly from command line ( for example like "mvn :::goal" )? BTW, the exception I got from using 2.0-beta-1-SNAPSHOT or 2.0-SNAPSHOT is java.lang.ClassCastException: java.util.HashMap at org.apache.maven.plugin.ant.AntBuildWriterUtil.getMavenPluginOptions(AntBuildWriterUtil.java:980) at org.apache.maven.plugin.ant.AntBuildWriterUtil.getMavenCompilerPluginOptions(AntBuildWriterUtil.java:778) at org.apache.maven.plugin.ant.AntBuildWriter.writeCompileTasks(AntBuildWriter.java:964) at org.apache.maven.plugin.ant.AntBuildWriter.writeCompileTarget(AntBuildWriter.java:652) at org.apache.maven.plugin.ant.AntBuildWriter.writeGeneratedBuildXml(AntBuildWriter.java:280) at org.apache.maven.plugin.ant.AntBuildWriter.writeBuildXmls(AntBuildWriter.java:112) at org.apache.maven.plugin.ant.AntMojo.execute(AntMojo.java:112) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) regards, Srinivasan Chikkala Open ESB Community (http://open-esb.org) Tim Kettler wrote: Hi, I can't say if this is the final root of your problem but you should start by fixing the repository definitions in your settings.xml and see if that helps: Srinivasan Chikkala schrieb: Any help on how to get the latest maven-ant-plugin ( maven-ant-plugin-2.0-SNAPSHOT.jar) ? I am trying to use the latest maven-ant-plugin, but when I execute "mvn ant:ant" after setting the settings.xml entry repo1 http://repo1.maven.org/maven2 central 'http://repo1.maven.org/maven2' *is* the URL of central, so you are effectivly mirroring central with itself. You can savely just leave that definition out. snapshot.apache.org http://people.apache.org/maven-snapshot-repository central 'http://people.apache.org/maven-snapshot-repository' *is not* a mirror of central. It contains just the snapshot releases of ASF artifacts. This should just be a regular repository definition in your settings [1]. -Tim [1] http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html [...] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Possible to have eclipse project files in archetype?
If I understood this correctly, you are trying to add a ".xyz" file in
your archetype. If that is correct, yes, you can add these files also in
the archetype. Just add them to the "archetype-resources" directory the
same way you add the other source or template files and update your
META-INF/maven/archetype.xml to include them in the resources. For
example, see the attached .project and .class file that I used for my
archetype that creates a maven project which also can be opened as a
pure eclipse project. I have used the "artifactId" variable in the
.project to specify the eclipse project display name.
META-INF/maven/archetype.xml
...
.project
.classpath
regards,
Srinivasan Chikkala
Open ESB Community (http://open-esb.org)
Mick Knutson wrote:
I want to know if it is possible to have and configure .project and
.classpath files for eclipse in my archetype?
JBI Binding Component[${artifactId}]
org.eclipse.jdt.core.javabuilder
org.eclipse.jdt.core.javanature
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: error getting maven-ant-plugin 2.0-SNAPSHOT
Thanks for the info. I fixed this part by removing the apache maven repository from the mirror and adding it as a repository ( I just copied the apache profile specified at http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html ) to my settings.xml. However, when I run "mvn ant:ant" it still picking up the "2.0-beta-1" from the central repository. So, I added the plugin configuration ( under ) explicitly in my project pom file to pick up the "2.0-beta-1-SNAPSHOT" and it downloaded and used that version, but got the exception using it. Another question is that if I don't want to configured the plugin in the project pom for a particular version of a plugin, what are my other options? Is the plugin registry the only option to force the mvn to use particular version of the plugin? how can I tell maven to use a particular version of the plugin using command line options when I am calling the plugin goal directly from command line ( for example like "mvn :::goal" )? BTW, the exception I got from using 2.0-beta-1-SNAPSHOT or 2.0-SNAPSHOT is java.lang.ClassCastException: java.util.HashMap at org.apache.maven.plugin.ant.AntBuildWriterUtil.getMavenPluginOptions(AntBuildWriterUtil.java:980) at org.apache.maven.plugin.ant.AntBuildWriterUtil.getMavenCompilerPluginOptions(AntBuildWriterUtil.java:778) at org.apache.maven.plugin.ant.AntBuildWriter.writeCompileTasks(AntBuildWriter.java:964) at org.apache.maven.plugin.ant.AntBuildWriter.writeCompileTarget(AntBuildWriter.java:652) at org.apache.maven.plugin.ant.AntBuildWriter.writeGeneratedBuildXml(AntBuildWriter.java:280) at org.apache.maven.plugin.ant.AntBuildWriter.writeBuildXmls(AntBuildWriter.java:112) at org.apache.maven.plugin.ant.AntMojo.execute(AntMojo.java:112) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) regards, Srinivasan Chikkala Open ESB Community (http://open-esb.org) Tim Kettler wrote: Hi, I can't say if this is the final root of your problem but you should start by fixing the repository definitions in your settings.xml and see if that helps: Srinivasan Chikkala schrieb: Any help on how to get the latest maven-ant-plugin ( maven-ant-plugin-2.0-SNAPSHOT.jar) ? I am trying to use the latest maven-ant-plugin, but when I execute "mvn ant:ant" after setting the settings.xml entry repo1 http://repo1.maven.org/maven2 central 'http://repo1.maven.org/maven2' *is* the URL of central, so you are effectivly mirroring central with itself. You can savely just leave that definition out. snapshot.apache.org http://people.apache.org/maven-snapshot-repository central 'http://people.apache.org/maven-snapshot-repository' *is not* a mirror of central. It contains just the snapshot releases of ASF artifacts. This should just be a regular repository definition in your settings [1]. -Tim [1] http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html [...] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
error getting maven-ant-plugin 2.0-SNAPSHOT
voke0(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) Caused by: org.apache.maven.plugin.version.PluginVersionResolutionException: Error resolving version for 'org.apache.mav en.plugins:maven-ant-plugin': Unable to read the metadata file for artifact 'org.apache.maven.plugins:maven-ant-plugin:p om': Error getting POM for 'org.apache.maven.plugins:maven-ant-plugin' from the repository: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata. org.apache.maven.plugins:maven-ant-plugin:pom:2.0-SNAPSHOT regards, -- Srinivasan Chikkala Open ESB Community (http://open-esb.org) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
