/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13802852
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
not that big of a problem, since Eclipse offers very decent refactoring
features to do that across different projects.
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13802852
Sent from the Maven - Users mailing list
the MANIFEST of B at compile time, find the
dependency on A and add the -SNAPSHOT suffix, so...
4. A's version as declared in the POM should actually be:
version1.0.0-SNAPSHOT/version
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2
convention) is that the prefix for
plugins is the reverse domain name of the company or organization, ie. mine
could be:
com.buggybrain.plugin1
com.buggybrain.plugin2
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13793981
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
of B at compile time, find the
dependency on A and add the -SNAPSHOT suffix, so...
4. A's version as declared in the POM should actually be:
version1.0.0-SNAPSHOT/version
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177
on A and add the -SNAPSHOT suffix, so...
4. A's version as declared in the POM should actually be:
version1.0.0-SNAPSHOT/version
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13789763
Sent from
and I thinkg the automatic pom generation doesn't create these by
default.
Let me know if this works and I'll update the article.
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13749166
Sent from the Maven
asking to work on the issue and have psteclipse
support the new jar placement in some near version of the plugin.
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13793438
Sent from the Maven - Users mailing list archive
wrote to Peter asking to work on the issue and have psteclipse
support the new jar placement in some near version of the plugin.
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13793438
Sent from the Maven - Users
for
plugins is the reverse domain name of the company or organization, ie. mine
could be:
com.buggybrain.plugin1
com.buggybrain.plugin2
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13793981
Sent from the Maven
plugins.
It's not that big of a problem, since Eclipse offers very decent refactoring
features to do that across different projects.
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13802852
Sent from the Maven - Users
://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13749166
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
are missing.
I actually made it work after some serious fighting. Here are the remaining
pieces, which were missing from the article:
http://www.buggybrain.com/2007/10/building-eclipse-plugins-with-maven-2.html
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse
OK, I really need this to work because I'm fed up with ant maintenance and
manual dependency management.
I've tried to start all over again. I think the problem might have come from
the fact that I was not using the original version of the mojos described by
the author of the article, but one
I finally found some lead to progress.
I managed to build and install the original version of the mojos.
Then I found something: it's all a problem of dependency versions. In my
source-plugin module manifest dependencies, I did not specify any version
for the plugins on which I depend, which
you can see an example of an eclipse plugin build with maven at
http://q4e.googlecode.com/svn/branches/built-with-maven/embedder/
On 10/26/07, Sebastien ARBOGAST [EMAIL PROTECTED] wrote:
I finally found some lead to progress.
I managed to build and install the original version of the mojos.
I'm trying to apply the instructions given in the Eclipse Corner article (
http://www.eclipse.org/articles/article.php?file=Article-Eclipse-and-Maven2/index.html)
in order to build several Eclipse plugins using Maven 2.0.4.
In the first part of the article there is something about a Deploy Mojo
I checked out the last version I could find in the m2eclipse project:
http://svn.codehaus.org/m2eclipse/maven-pst
That's the one I'm using with a few modifications to the POM in order to
build against Maven 2.0.7 and Eclipse 3.3.1
Now here are the error messages that I get:
[INFO]
Hi Sebastien,
I know I once made it work, but I remember I had to download some more
recent code than the one which is mentioned on the article. I'd argue
that the authors of the article did a great job making me understand
what the problem is after all and explaining why they made the design
I have started looking at what would need to be done in order to build
Eclipse plugins using Maven 2.
The general idea is that POM files could be generated using information in
the plugins' manifest.mf, plugin.xml and build.properties files. At first
glance, the required information
This would be a wonderful idea.
I'd particularly welcome easy ways to run JUnit tests on plugins from maven.
good luck,
Benedict
Andrew Niefer wrote:
I have started looking at what would need to be done in order to build
Eclipse plugins using Maven 2.
The general idea is that POM files could
On Wed, 2005-09-07 at 16:58 -0400, Andrew Niefer wrote:
I have started looking at what would need to be done in order to build
Eclipse plugins using Maven 2.
The general idea is that POM files could be generated using information in
the plugins' manifest.mf, plugin.xml and
At 04:58 PM 9/7/2005, Andrew Niefer wrote:
I have started looking at what would need to be done in order to build
Eclipse plugins using Maven 2.
... snip ...
The install phase would be different from the normal m2 install. We would
need to gather the jars and any additional resources into
Jason van Zyl [EMAIL PROTECTED] wrote on 09/07/2005 05:29:45 PM:
Might you have an ViewCVS URL of an example plugin, or set of plugins,
that we can work against while discussing this?
It was suggested on the eclipse pde-build mailing list that building the
eclipse plugins that make up the
What about from a pom.xml, maven can generate
manifest.fmhttp://manifest.fmfile.
There is already some work done at
http://svn.apache.org/repos/asf/incubator/felix/trunk/tools/maven2/maven-osgi-plugin/
-D
On 9/7/05, Andrew Niefer [EMAIL PROTECTED] wrote:
Jason van Zyl [EMAIL
26 matches
Mail list logo
