I am having an issue setting jar versions in Maven and trying to resolve this
through Best Practices
What I have is my project pom.xml that will build project MyJar. In the Pom,
I have dependencies setup like this
org.apache
xalan
${xalanVersion}
In my settings.xml,
task and what it expects. Any
thoughts?
Regards,
Mark
Michael McCallum-3 wrote:
>
> release:prepage tags
> release:perform builds from tag and deploys to repo...
>
> On Wednesday 31 October 2007 08:31, Mark_E wrote:
>> Hello,
>> I am trying to automate my tagging pr
Hello,
I am trying to automate my tagging process in Subversion through Maven and
I am running into issues. I am not sure I am using Maven correctly to do
this so I wanted to ask the question here...
Basically, I have a POM for my project and it has the scm connection
information as well as the
b needs the jar
>> files to work (like a utility library)?
>>
>> This is the "Maven way" to do things. Of course, you can do it however
>> you want, but I generally find it easiest to just do what Maven is
>> expecting.
>>
>> Wayne
>
t;Maven way" to do things. Of course, you can do it however
> you want, but I generally find it easiest to just do what Maven is
> expecting.
>
> Wayne
>
> On 10/18/07, Mark_E <[EMAIL PROTECTED]> wrote:
>>
>> Hi Wayne,
>
t; and/or send the poms for diagnosis.
>
> Wayne
>
> On 10/18/07, Mark_E <[EMAIL PROTECTED]> wrote:
>>
>> Hello,
>> I am running into a strange situation with the maven-ejb-plugin and
>> maven-jar-plugin
>>
>> I am performing a build, building
Hello,
I am running into a strange situation with the maven-ejb-plugin and
maven-jar-plugin
I am performing a build, building a jar and an ejb. Seems that when I
execute the ejb plugin during the package phase, it messes up the execution
of the maven-jar-plugin.
For example, I am using the sna
Hello,
In one of my projects, I not only build the default project jar, but I
also invoke a simple Ant Task to jar some optional classes into another jar.
These classes cannot live in the default jar but I need to put them into the
maven repository so that another project, that depends on them a
Hello,
I have started to work with the maven-release-plugin and I am running into
a strange exception.
I run the following command: mvn release:prepare -DdryRun=true
And here is the error:
[ERROR] FATAL ERROR
[INFO]
[IN
Hello Wayne,
Thanks for the information. I will take a look at that plugin.
Regards,
Mark
Wayne Fay wrote:
>
> The release plugin solves most people's version issues.
>
> Wayne
>
> On 10/15/07, Mark_E <[EMAIL PROTECTED]> wrote:
>>
>> Hello,
>
Hello,
I have been using Maven for about a month now and I really like it
however, I am having an issue with setting jar versions and I was looking
for suggestions on how other people do it.
I basically have a pom for each project I build. In the pom.xml I have the
dependencies. We typically ve
Hi Emmanuel,
Thanks very much. That worked. I should have searched harder, I would
have found the file!
:working:
Regards,
Mark
--
View this message in context:
http://www.nabble.com/No-Mail-being-sent-with-version-1.1-beta-2-tf4438386.html#a12675179
Sent from the Continuum - Users mailing
Hi Wendy,
Thanks for the suggestion. I actually have 1.0.3 running now and I like
it so I look forward to the improvements/enhancements in the 1.1 beta. I'll
certainly take a look at it.
Regards,
Mark
--
View this message in context:
http://www.nabble.com/Problem-Performing-Build---Versio
I figured it out. Well, I actually got it working by upgrading the
velocity-1.4 jars to the velocity-1.5 jars. Now I am able to build.
Mark
--
View this message in context:
http://www.nabble.com/Problem-Performing-Build---Version-1.0.3-tf4430122.html#a12643881
Sent from the Continuum - Users ma
14 matches
Mail list logo
