Does anyone actually use pde mode in maven-eclipse-plugin?
The support looks pretty basic and there are other better options like
tycho and felix for doing this stuff.
EclipseOSGiManifestWriter has been deprecated in favour of felix and I
wonder whether its worth keeping the other stuff around.
Try to only escape the '$' character, see
http://velocity.apache.org/engine/devel/user-guide.html#escapinginvalidvtlreferences
HTH,
-Lukas
On 09/23/2011 12:12 AM, Params wrote:
Thanks Robert, I tried couple of combinations and found this to work:
value#set($varline =
Hello,
my question is about how SNAPSHOT dependencies between submodules in multi
module projects can be automatically incremented when performing a release.
Let's give an example: I've a multi module project P with two sub modules A and
B. Current version is 1.0-SNAPSHOT. The version number
I thought that the release plugin handled this. But I have never
tried, as I always use the ${project.version} property for specifying
version within a multi-module project. That would solve your problem.
/Anders
On Fri, Sep 23, 2011 at 12:08, Abid Hussain hussain.d...@gmx.de wrote:
Hello,
my
Hi Abid,
Abid Hussain wrote:
Hello,
my question is about how SNAPSHOT dependencies between submodules in multi
module projects can be automatically incremented when performing a
release.
Let's give an example: I've a multi module project P with two sub modules
A and B. Current version
Thanks Barrie!
That modification made the trick.
I also don't actually know if configuring the plugin using the command
line properties is a best practice.
But seeing the source code of the eclipse plugin, I traced it to the
IdeUtils.java [1], and it seems that the properties are not tacked
into
Hello,
e.g. there is a project A (e.g. 1.0-SNAPSHOT) which has a dependency to another
non-released project B (e.g. 2.3-SNAPSHOT).
AFAIK performing a release which has SNAPSHOT versions is not possible.
Is there a way to tell maven that when a release of project A should be
performed to
I hope not!
Sounds like a really bad thing to do.
How does maven know that B is release quality?
Ron
On 23/09/2011 11:58 AM, Abid Hussain wrote:
Hello,
e.g. there is a project A (e.g. 1.0-SNAPSHOT) which has a dependency to another
non-released project B (e.g. 2.3-SNAPSHOT).
AFAIK
Hi,
The Mojo team is pleased to announce the release of the Exec-Maven-Plugin
version 1.2.1.
This plugin provides 2 goals to help execute system and Java programs.
http://mojo.codehaus.org/exec-maven-plugin/
To get this update, simply specify the version in your project's plugin
All,
1. I have following directory for java source code
--lion
--com
test1 -- contains pom.xml and java source code with package
com.test1
test2 - contains pom.cml and java source code with pakage
com.test2
when compiler plugin compiles it does directory
On Sat, Sep 24, 2011 at 12:43 AM, Gabriel Belingueres
belingue...@gmail.com wrote:
Thanks Barrie!
That modification made the trick.
I also don't actually know if configuring the plugin using the command
line properties is a best practice.
But seeing the source code of the eclipse plugin, I
Fri, 23 Sep 2011 14:12:00 -0400, /Gupta, Narendra/:
1. I have following directory for java source code
--lion
--com
test1 -- contains pom.xml and java source code with package
com.test1
test2 - contains pom.cml and java source code with pakage
com.test2
On 17/09/2011, at 12:37 AM, Stuart Sierra wrote:
I use Git, maven-release-plugin, Hudson, and the Hudson M2 Release
Plugin. Can I perform a release from a Git branch other than master?
On Mon, Sep 19, 2011 at 4:17 AM, Brett Porter br...@apache.org wrote:
I believe so. You may need to set the
13 matches
Mail list logo