Re: Eclipse as a dependency
I believe that openArchitectureWare also uses the eclipse-formatter. At least they have several eclipse-jars in their repo (although I honestly have no idea how old/new thea are). You might want to check those out? http://www.openarchitectureware.org/m2/ Roland there are some jars already there from an attempt long time ago to have eclipse in the repository, under org.eclipse On Fri, Sep 25, 2009 at 2:00 AM, Emmanuel Hugonnet ehsavoi...@gmail.com wrote: Hi, I have created a small Maven plugin which uses the Eclipse code formatter to format my code. I would like to release it but the available librairies of Eclipse are quite old and I don't want my users to have Eclipse installed (that's the whole point of the plugin). Is there a repository with Eclipse jars somewhere ? I think that m2eclipse/tycho should be using them but I can't seem to find the jars. What's the policy concerning these jars ? Thans, Emmanuel - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Eclipse as a dependency
Hi, I have created a small Maven plugin which uses the Eclipse code formatter to format my code. I would like to release it but the available librairies of Eclipse are quite old and I don't want my users to have Eclipse installed (that's the whole point of the plugin). Is there a repository with Eclipse jars somewhere ? I think that m2eclipse/tycho should be using them but I can't seem to find the jars. What's the policy concerning these jars ? Thans, Emmanuel
Re: Eclipse as a dependency
there are some jars already there from an attempt long time ago to have eclipse in the repository, under org.eclipse On Fri, Sep 25, 2009 at 2:00 AM, Emmanuel Hugonnet ehsavoi...@gmail.com wrote: Hi, I have created a small Maven plugin which uses the Eclipse code formatter to format my code. I would like to release it but the available librairies of Eclipse are quite old and I don't want my users to have Eclipse installed (that's the whole point of the plugin). Is there a repository with Eclipse jars somewhere ? I think that m2eclipse/tycho should be using them but I can't seem to find the jars. What's the policy concerning these jars ? Thans, Emmanuel - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with eclipse-plugin and dependency-maven-plugin
http://jira.codehaus.org/browse/MDEP-27 The problem seems not to be related to the eclipse-plugin only. It occurs also in conjunction with other plugins or lifecycle-phases. -- View this message in context: http://www.nabble.com/Problem-with-eclipse-plugin-and-dependency-maven-plugin-tf1861928.html#a5148090 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with eclipse-plugin and dependency-maven-plugin
Hi all,
I encountered a weird problem with the eclipse-plugin in conjunction with
the dependency-plugin.
In my project, an attached artifact from another project, wich contains a
MagicDraw model should be unpacked in the initialize phase. The
configuration for the dependency-plugin looks like this:
...
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddependency-maven-plugin/artifactId
version1.0/version
inheritedfalse/inherited
executions
execution
phaseinitialize/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdaGroupId/groupId
artifactIdanArtifactId/artifactId
versionaVersion/version
typezip/type
classifiermd/classifier
outputDirectory${project.build.directory}\dependencies/outputDirectory
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
/plugins
/build
...
This works fine so long.
When I now try to generate eclipse project files for this project by calling
mvn eclipse:eclipse I get the following error message:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] One or more required plugin parameters are invalid/missing for
'dependency:unpack'
[0] inside the definition for plugin: 'dependency-maven-plugin'specify the
following:
configuration
...
artifactItemsVALUE/artifactItems
/configuration.
If I change the execution phase in the dependency-plugin configurtion from
initialize to process-resources and call the eclipse-plugin again, it
works fine.
Any phase prior to process-resources causes the eclipse-plugin to fail.
Does somebody has an idea, what's going wrong?
Thanx,
Markus
--
View this message in context:
http://www.nabble.com/Problem-with-eclipse-plugin-and-dependency-maven-plugin-tf1861928.html#a5085617
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with eclipse-plugin and dependency-maven-plugin
sound like a bug, please file a JIRA
On 6/28/06, mawi [EMAIL PROTECTED] wrote:
Hi all,
I encountered a weird problem with the eclipse-plugin in conjunction with
the dependency-plugin.
In my project, an attached artifact from another project, wich contains a
MagicDraw model should be unpacked in the initialize phase. The
configuration for the dependency-plugin looks like this:
...
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddependency-maven-plugin/artifactId
version1.0/version
inheritedfalse/inherited
executions
execution
phaseinitialize/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdaGroupId/groupId
artifactIdanArtifactId/artifactId
versionaVersion/version
typezip/type
classifiermd/classifier
outputDirectory${project.build.directory}\dependencies/outputDirectory
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
/plugins
/build
...
This works fine so long.
When I now try to generate eclipse project files for this project by
calling
mvn eclipse:eclipse I get the following error message:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] One or more required plugin parameters are invalid/missing for
'dependency:unpack'
[0] inside the definition for plugin: 'dependency-maven-plugin'specify the
following:
configuration
...
artifactItemsVALUE/artifactItems
/configuration.
If I change the execution phase in the dependency-plugin configurtion from
initialize to process-resources and call the eclipse-plugin again, it
works fine.
Any phase prior to process-resources causes the eclipse-plugin to fail.
Does somebody has an idea, what's going wrong?
Thanx,
Markus
--
View this message in context:
http://www.nabble.com/Problem-with-eclipse-plugin-and-dependency-maven-plugin-tf1861928.html#a5085617
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Eclipse Plugin] Defining dependency as Eclipse project
Hello, I tried to define an Eclipse project as dependency in the project.xml. But after calling maven eclipse maven tries to download a JAR instead of adding an entry to the .classpath file. I used the sample code at http://maven.apache.org/reference/plugins/eclipse/. Did I misunderstand something? I thought thats the way to add a required project to the build path using maven. Regards, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Eclipse Plugin] Defining dependency as Eclipse project
Martin Burger wrote: Hello, I tried to define an Eclipse project as dependency in the project.xml. But after calling maven eclipse maven tries to download a JAR instead of adding an entry to the .classpath file. I used the sample code at http://maven.apache.org/reference/plugins/eclipse/. Did I misunderstand something? I thought thats the way to add a required project to the build path using maven. Regards, Martin The maven eclipse plugin just includes the artifacts from the maven repository for you. It does not create dependencies between eclipse projects (even though this would be desirable for SNAPSHOT dependencies). AFAIK this can't be done with the current eclipse plugin, because it does not know about the other projects in your eclipse workspace and their locations in the filesystem. Maybe Maven 2.0 can do that. I'm waiting for the first beta release before I give it a try. Edmund - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Eclipse Plugin] Defining dependency as Eclipse project
Im quoting the answer of Tomas for about the same question i made few months ago: ... eclipse.dependency does not refer to an Eclipse project but only tells the Eclipse plugin whether it should add the dependency to the project's classpath. Since an Eclipse project is not recognized as a dependency type, the dependency you have defined will not be considered as an Eclipse project and automatically added to the classpath. However, you can add an Eclipse project to the classpath by defining the following in your project.properties file: maven.eclipse.classpath.include=/test1 Then you also need set eclipse.dependency to false in your project.xml. If not, you'll add it once as an Eclipse dependency and a second time as jar dependency. ... As you can see eclipse.dependency will download the jar and work with it only for other maven goals but in your eclipse project will be linked the eclipse project where the property was set. Best regards. []'s On 6/30/05, Edmund Urbani [EMAIL PROTECTED] wrote: Martin Burger wrote: Hello, I tried to define an Eclipse project as dependency in the project.xml. But after calling maven eclipse maven tries to download a JAR instead of adding an entry to the .classpath file. I used the sample code at http://maven.apache.org/reference/plugins/eclipse/. Did I misunderstand something? I thought thats the way to add a required project to the build path using maven. Regards, Martin The maven eclipse plugin just includes the artifacts from the maven repository for you. It does not create dependencies between eclipse projects (even though this would be desirable for SNAPSHOT dependencies). AFAIK this can't be done with the current eclipse plugin, because it does not know about the other projects in your eclipse workspace and their locations in the filesystem. Maybe Maven 2.0 can do that. I'm waiting for the first beta release before I give it a try. Edmund - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Nobody knows who i really am I never felt this empty before And if I never need someone to come along Who's gonna comfort me and keep me strong? -- Marcell Manfrin Barbacena [EMAIL PROTECTED] MSN Messenger: [EMAIL PROTECTED] ICQ UIN: 63671762 Skype: callto://marcell84bruk +55 (83) 8808-8555 (Oi) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Eclipse Plugin] Defining dependency as Eclipse project
Edmund Urbani schrieb am 30.06.2005 09:36: The maven eclipse plugin just includes the artifacts from the maven repository for you. It does not create dependencies between eclipse projects (even though this would be desirable for SNAPSHOT dependencies). AFAIK this can't be done with the current eclipse plugin, because it does not know about the other projects in your eclipse workspace and their locations in the filesystem. Mmh, quoted from http://maven.apache.org/reference/plugins/eclipse/: The dependencies defined in the POM need not to be jars strictly. They can be projects in the eclipse workspace. If a dependency is an eclipse project a property needs to be added to that dependency to indicate so. They can be projects in the eclipse workspace. Does this not say that it's possible to add a project instead of a JAR? Regards Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Eclipse Plugin] Defining dependency as Eclipse project
Marcell Manfrin Barbacena schrieb am 30.06.2005 10:02: However, you can add an Eclipse project to the classpath by defining the following in your project.properties file: maven.eclipse.classpath.include=/test1 This adds E:/test1 to the .classpath as classpathentry (note the drive letter). BTW, I think the documentation on http://maven.apache.org/reference/plugins/eclipse/ is misleading. Regards, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Eclipse Plugin] Defining dependency as Eclipse project
I agree with you that the docs are misleading...
Try that then:
maven.eclipse.classpath.include=${maven.eclipse.workspace}/project
[]'s
On 6/30/05, Martin Burger [EMAIL PROTECTED] wrote:
Marcell Manfrin Barbacena schrieb am 30.06.2005 10:02:
However, you can add an Eclipse project to the classpath
by defining the following in your project.properties file:
maven.eclipse.classpath.include=/test1
This adds E:/test1 to the .classpath as classpathentry (note the drive
letter).
BTW, I think the documentation on
http://maven.apache.org/reference/plugins/eclipse/ is misleading.
Regards,
Martin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Nobody knows who i really am
I never felt this empty before
And if I never need someone to come along
Who's gonna comfort me and keep me strong?
--
Marcell Manfrin Barbacena
[EMAIL PROTECTED]
MSN Messenger: [EMAIL PROTECTED]
ICQ UIN: 63671762
Skype: callto://marcell84bruk
+55 (83) 8808-8555 (Oi)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
