Re: Treat maven warnings as errors

2017-03-06 Thread Gordon Cody
Hello Yaron

You may find this an impossible task to accomplish. The standard maven
plugins generally do a good job with their messages but some 3rd-party jars
and plugins log WARNING messages, a few even log ERROR messages when the
developer really should have used INFO or possibly logged nothing at all.

Mostly these messages would show up in the logs when you run your
junit/surefire tests but some can come even when you build with
skipTests=true.
How far you get will depend on your projects dependencies and the set of
plugins you use in your builds.

I wish you luck.

Just my personal opinion, Gordon

On Mon, Mar 6, 2017 at 8:25 PM, Daniel Schulz 
wrote:

> Hi,
>
> Might this help you?
>
> https://maven.apache.org/plugins/maven-dependency-
> plugin/examples/failing-the-build-on-dependency-analysis-warnings.html
>
> http://stackoverflow.com/questions/9192613/how-do-i-
> get-a-java-maven-build-to-fail-for-compiler-warnings
>
> Kind regards, Daniel.
>
>
> > On 06.03.2017, at 15:58, Yaron Golan  wrote:
> >
> > Anyone?
> >
> > "No" is an answer as well, you know ... :)
> >
> >
> > -Original Message-
> > From: Yaron Golan [mailto:ygo...@interwise.com]
> > Sent: Wednesday, March 01, 2017 12:05 PM
> > To: users@maven.apache.org
> > Subject: Treat maven warnings as errors
> >
> > Hi,
> > Is there a way to treat the maven warnings as errors?
> >
> >
> >
> > -
> > 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
>
>


-- 
Best Regards, Gord Cody

Senior Release Manager  Zafin Inc.
179 Colonnade Road-Suite 100, Ottawa ON, Canada
Phone: +1 (613) 216-2504  Fax: +1 (613) 688-1374  Mobile: +1 613-601-2734
Web: http://zafin.com  Email: gordon.c...@zafin.com


Re: Create test jar during build without attaching

2016-08-19 Thread Gordon Cody
Perhaps I don't understand what is meant by "not attaching" but if all you
want to do is skip deployment, the maven-deploy-plugin has this feature:

true

which can be added to the module you do not wish to deploy. We use this in
order to not deploy .ear files to our artifactory.

Regards, Gord Cody

On Fri, Aug 19, 2016 at 1:37 PM, Karl Heinz Marbaise 
wrote:

> Hi,
>
> On 19/08/16 03:36, Christopher wrote:
>
>> Hi Maven Users list,
>>
>> What's the best way to create a jar during a build without attaching it?
>>
>> Currently, our pom is configured to use the maven-jar-plugin to create it,
>> but that plugin attaches an artifact, which gets deployed. We don't want
>> that. That doesn't seem to be configurable.
>>
>
> Can you describe why you would like to create a jar which shouldn't be
> deployed ? May be we can enhance maven-jar-plugin to support such a use
> case?
>
>
> Kind regards
> Karl Heinz Marbaise
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Best Regards, Gord Cody

Release Manager  Zafin Labs Americas Inc.
179 Colonnade Road-Suite 100, Ottawa ON, Canada
Phone: +1 (613) 216-2504  Fax: +1 (613) 688-1374  Mobile: +1 613-601-2734
Web: http://zafin.com  Email: gordon.c...@zafin.com

-- 
Zafin - Canada

-- 
http://zafin.com



--

Connect with us

  
  

News and Events

Zafin announces 100 person Center of Excellence in Toronto 


For the 2nd consecutive year, Zafin named to the Deloitte Fast 50 and Fast 
500 rankings 





Re: Fail fast for 401 Unauthorized failures

2016-07-27 Thread Gordon Cody
Docs are not always accurate. Sometimes they are simply not up to date.

All of our GET/PUT requests include credentials on the first attempt. This
is from our settings.xml. Notice the tag ,


  someID
  someUser
  somePassword
  
httpclient

  
true
  

  


Regards, Gord Cody

On Wed, Jul 27, 2016 at 2:34 AM, Tomasz Juchniewicz 
wrote:

> Probably not. Following docs preemptive authentication is for PUT requests.
> I have a problem with downloading.
>
> 2016-07-25 20:43 GMT+02:00 Mirko Friedenhagen :
>
> > Hello,
> >
> > maybe
> >
> >
> https://maven.apache.org/guides/mini/guide-http-settings.html#Example:_Using_Preemptive_Authentication
> > could help.
> > Regards
> > Mirko
> > --
> > Sent from my mobile
> >
> > Am 25.07.2016 15:11 schrieb "Tomasz Juchniewicz"  >:
> >
> > > Hi,
> > >
> > > I'm working in corporate environment with strict password locking
> > policies.
> > > After 5 authentication errors my account is locked.
> > >
> > > My problem is that Maven tries to download artifacts and not every
> error
> > > (e.g. downloading maven-metadata.xml) causes to stop the build and this
> > > leads to account lock. Any idea to make Maven fail fast after first
> > > authentication problem.
> > >
> > >
> > >
> > > --
> > > TJu
> > >
> >
>
>
>
> --
> TJu
>



-- 
Best Regards, Gord Cody

Release Manager  Zafin Labs Americas Inc.
179 Colonnade Road-Suite 100, Ottawa ON, Canada
Phone: +1 (613) 216-2504  Fax: +1 (613) 688-1374  Mobile: +1 613-601-2734
Web: http://zafin.com  Email: gordon.c...@zafin.com

-- 
Zafin - Canada

-- 
http://zafin.com



--

Connect with us

  
  

News and Events

Zafin announces 100 person Center of Excellence in Toronto 


For the 2nd consecutive year, Zafin named to the Deloitte Fast 50 and Fast 
500 rankings 





Re: Maven and pre-emptive authentication

2015-03-30 Thread Gordon Cody
Hello James

It really does try twice. The first time it tries with no credentials
supplied.
This came to our attention when we upgraded from maven-2.0.9 to maven-3.0.5.

We found out at that time that it had to do with being compliant to some
web specification and there was no way to force it to use credentials on
the first attempt.

The delay is a mere fraction of a second for most files. On larger files it
can be slightly irritating.
We now avoid deploying ear files altogether by using the skip argument of
the deploy plugin.


Regards, Gord Cody



On Mon, Mar 30, 2015 at 4:34 AM, James Green james.mk.gr...@gmail.com
wrote:

 I am a little confused. According to:

 https://maven.apache.org/guides/mini/guide-http-settings.html

 Maven 3.0.4 defaults to pre-emptive authentication for HTTP PUTs.

 According to my haproxy logs, each PUT is done twice:

 1. PUT happens, receives a 401 response from Nexus
 2. PUT happens, receives a 201 response from Nexus

 Our installed version:
 ii  maven 3.0.4-2
   Java software project management and comprehension tool

 Is the documentation simply wrong or am I somehow mis-interpreting things?

 Thanks,

 James




-- 
Best Regards, Gord Cody

Release Manager  Zafin Labs Americas Inc.
179 Colonnade Road-Suite 100, Ottawa ON, Canada
Phone: +1 (613) 216-2504  Fax: +1 (613) 688-1374  Mobile: +1 613-601-2734
Web: http://zafin.com  Email: gordon.c...@zafin.com

-- 
Zafin - Canada

-- 
http://zafin.com

http://zafin.com/

--

Connect with us

 http://www.youtube.com/user/ZafinGlobal  
http://www.linkedin.com/company/Zafin  http://twitter.com/Zafin

News and Events

Zafin joins the Deloitte Fast 50 and Fast 500 Rankings 
http://zafin.com/press-releases/zafin-ranks-16th-on-the-2014-deloitte-technology-fast-50-list/

http://zafin.com/press-releases/zafin-ranks-16th-on-the-2014-deloitte-technology-fast-50-list/


unit tests with multiple oracle, db2 etc

2014-05-23 Thread Gordon Cody
We have to begin running junit tests using more than 1 database type. I am
wondering how best to run all unit tests using oracle then run all of the
tests again using db2 then postgres. I figured some of you out there must
have a similar requirement.

Currently we have test/resources/test-context.xml that contains
bean id=dataSource
class=org.apache.commons.dbcp.BasicDataSource
destroy-method=close lazy-init=true
property name=driverClassName
value=com.p6spy.engine.spy.P6SpyDriver /
property name=url value=jdbc:oracle:thin:@localhost:1521:
/
property name=username value=x /
property name=password value=x /
property name=accessToUnderlyingConnectionAllowed value=true /
property name=defaultAutoCommit value=false /
property name=maxWait value=0 /
property name=maxActive value=-1 /
/bean

There is nothing in the pom.xml explicitly related to unit tests other than
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.8.2/version
/dependency

Quick sanity builds are done by our CI system using
mvn package -e -Dmaen.test.skip=true
Due to how long the tests take to complete they are only run daily using
mvn test -e -Dtest=com.zafinlabs.someapp.somemodule.TestSomeProcess

Suggestions please.
-- 
Best Regards, Gord Cody

Release Manager  Zafin Labs Americas Inc.
179 Colonnade Road-Suite 100, Ottawa ON, Canada
Phone: +1 (613) 216-2504  Fax: +1 (613) 688-1374  Mobile: +1 613-601-2734
Web: http://zafin.com  Email: gordon.c...@zafin.com

-- 
Zafin - Canada

-- 
http://zafin.com

http://zafin.com/

--

Connect with us

 http://www.youtube.com/user/ZafinGlobal 
http://www.linkedin.com/company/Zafin
  http://twitter.com/Zafin

News and Events

Zafin among Top 10 FinTech Companies to Watch in 2014: American 
Bankerhttp://zafin.com/zafin-among-top-10-fintech-companies-to-watch-in-2014-american-banker/


Re: maven-deploy-plugin: exclude specific project artifact(s)?

2014-01-21 Thread Gordon Cody
Hello

We use this to prevent deploying ears/wars into our repo. Everything is
built but not everything gets deployed.
Newer versions of the deploy plugin allow you to skip deployment so within
a few specific poms you can add.

  plugin
artifactIdmaven-deploy-plugin/artifactId
version2.8.1/version
configuration
  skiptrue/skip
/configuration
  /plugin

This should work as long as you assemble each piece separately (each has
its own pom.xml) so divide and conquer.
Hope this helps.

-- 
Best Regards, Gord Cody

Release Manager  Zafin Labs Americas Inc.
179 Colonnade Road-Suite 100, Ottawa ON, Canada
Phone: +1 (613) 216-2504  Fax: +1 (613) 688-1374  Mobile: +1 613-601-2734
Web: http://zafin.com  Email: gordon.c...@zafin.com

-- 
Zafin - Canada

-- 
http://zafin.com

http://zafin.com/

--

Connect with us

 http://www.youtube.com/user/ZafinGlobal 
http://www.linkedin.com/company/Zafin
  http://twitter.com/Zafin

News and Events

Zafin among Top 10 FinTech Companies to Watch in 2014: American 
Bankerhttp://zafin.com/zafin-among-top-10-fintech-companies-to-watch-in-2014-american-banker/


Re: AW: AW: AW: mvn release:prepare does not update parent version

2013-11-09 Thread Gordon Cody
You may want to upgrade maven itself once more. It is not just maven itself
but the combination of plugins that are used and your environment matters.
Ensure that each maven goal you plan on using in your environment actually
works in your environment before you need it for real. Maven has to work
with your vcs, your artifact mgmt (nexus/artifactory/other), your network
security policies, etc. all at the same time.

When we began upgrading existing projects from mvn-2.0.9 we had to also
upgrade numerous plugins. It took some effort to find the combination of
plugins/configuration that allowed us to do 'mvn deploy' successfully with
mvn-3.0.4. But 'mvn release' did not work in our environment until
mvn-3.0.5 was released!!. Underlying plugin(s) had changed.

Regards, Gord


On Sat, Nov 9, 2013 at 4:55 AM, Markus Karg k...@quipsy.de wrote:

 Robert,

 no need to teach me about completeness of reports -- I am in the reverse
 situation day by day as you can imagine. The problem was that I had the
 problem since I migrated to Maven 3 from day one with even the smallest
 possible POM (it looked 'obvious' to me) and did not have the idea there
 might be a fix already already which is not contained in Maven 3 so far. In
 fact this is why I would love to have the ability to use version ranges in
 plugin dependencies! ;-)

 Anyways, as all is fixed now, thanks for the kind help! :-)
 -Markus

 -Original Message-
 From: Robert Scholte [mailto:rfscho...@apache.org]
 Sent: Freitag, 8. November 2013 18:52
 To: Maven Users List
 Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version

 Op Fri, 08 Nov 2013 16:30:30 +0100 schreef Markus Karg k...@quipsy.de:

  I wonder why someone fixed it but didn't close
  https://jira.codehaus.org/browse/MRELEASE-837...!

 Well, is was probably already fixed for a long time. Since you only had a
 description it will take some time to fix it, since it must first be
 reproducible. That's why attaching a sample project helps, and a patch with
 a possible fix even more.

 In this case it was the log-file which triggered me: first update the
 version of the plugin and see if it has been already been fixed.

 It is all about being as complete as possible :)

 Robert

 -
 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




-- 
Best Regards, Gord Cody

Release Manager  Zafin Labs Americas Inc.
179 Colonnade Road-Suite 100, Ottawa ON, Canada
Phone: +1 (613) 216-2504  Fax: +1 (613) 688-1374  Mobile: +1 613-601-2734
Web: http://zafin.com  Email: gordon.c...@zafin.com


Re: Maven versions in compilation

2013-10-01 Thread Gordon Cody
The first project I was switching to mvn3 I was also skeptical about the
ear produced being the same.

You must ensure both mvn2 and mvn3 use the same version of java (check
using mvn -version)

Separately explode the ear created by each version of mvn (lets call them A
and B) and and all war files within each ear using winzip or 7zip or some
other tool.
Use windiff to compare the exploded folders getting it to show any files
only in A or or only B and anything not identical.

There should not be any files that are only in one set or the other. All
differences have to be investigated. Only items that contain
date/timestrings or timestamps should show up. These may appear in your
manifest.mf (time of build) . Some 3rd party tools put date/time objects
into files also (e.g. flex).  These would also show as differences. Any
jars with differences need to be exploded so you can see which file(s) are
different inside of them. Looking at the differences in class files is
doable also but not pretty.

Regards, Gord Cody
gordon.c...@zafin.com


I


On Tue, Oct 1, 2013 at 3:30 PM, John Dix john@amdocs.com wrote:

 I have a question in order to make our dev managers warm and fuzzy.

 My understanding is that a pom that compiles under 2.1.0 and 3.0.5
 produces the same jars. I know this to be true so long as either version of
 Maven is pulling down the correct versions of SDK's used to build the java
 files but I need some kind of official stamp on that to ease nervousness.

 Thanks!

 John Caolan Dix
 Programming Sr. SME, Digital Commerce
 Amdocs Digital Services Division
 o: 206-288-0334 m: 425.351.7340

 AMDOCS | EMBRACE CHALLENGE EXPERIENCE SUCCESS

 Did you know...?
 Amdocs Mobile Payments enables operators to manage any number of app
 stores, merchants and aggregators and generate revenues from digital
 content and mobile commerce

 Follow Amdocs on Facebookhttp://www.facebook.com/amdocsinc/, Twitter
 http://twitter.com/AmdocsInc, LinkedIn
 http://www.linkedin.com/company/amdocs, YouTube
 http://www.youtube.com/amdocsinc and Google+
 https://plus.google.com/105657940751678445194 - and read the latest on
 the Amdocs blog networkhttp://blogs.amdocs.com/.



 This message and the information contained herein is proprietary and
 confidential and subject to the Amdocs policy statement,
 you may review at http://www.amdocs.com/email_disclaimer.asp




-- 
Best Regards, Gord Cody

Release Manager  Zafin Labs Americas Inc.
179 Colonnade Road-Suite 100, Ottawa ON, Canada
Phone: +1 (613) 216-2504  Fax: +1 (613) 688-1374  Mobile: +1 613-601-2734
Web: http://zafin.com  Email: gordon.c...@zafin.com


Re: Bootstraping a repository manager

2011-05-19 Thread Gordon Cody
Hi Gus

We seriously considered trying to implement the type of controls
 you talked about, but there are literally thousands of files you would
have to manually install once you figure out what they all are.

What we ended up doing was using the mirroOf feature in settings.xml
and allow artifactory to download what it needed and keep it forever.
We ran each of the standard mvn commands (and some others) that
developers use, in order to populate our artifactory.

Once we had all the necessary 3rd party bits  pieces we required, we
configured artifactorys 'global offline' mode. Subsequently new jars or
new versions of jars are only added manually after approval.

Prior to working like this we got burned (once) when an artifact we
required (a dependency of a dependency) was missing when we were
trying to do a release. That was a bad day we will not ever repeat.

-Gord

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



reconciling svn repository permissions vs maven trunk/tags/branches

2011-01-07 Thread Gordon Cody
Hello List

Svn repositories allow for access permissions to be set at the directory
level.

Maven seems to expect that developers have access to the entire repository.

Is there a way to reconcile these differences such that some people (for
example
junior, qa or non technical people have access only to certain portions of
the repo?

Regards, Gord
gc...@zafinlabs.com


Re: reconciling svn repository permissions vs maven trunk/tags/branches

2011-01-07 Thread Gordon Cody
Hello

Our svn repos are configured with only trunk/tags/branches
at the top level. If I remember correctly this is recommended
by maven.

I suppose in theory there is no reason not to have other
top level folders as long as maven ignores them.
Is anyone doing this?

Our developers need access to any active branches
and the trunk. They are also allowed to create their own
tags as long as they dont collide with release tags.

We now have documenters/testers/mgrs that are not
experienced with svn so I was asked to investigate
limiting their access. Unless there is a nice ui to manage
this it seems to me like it could quickly turn into
an administrative blackhole.

I really appreciate your mentioning that client bug btw, that
would have caught me (given our version)

Regards, Gord
gc...@zafinlabs.com

On Fri, Jan 7, 2011 at 5:01 PM, Dennis Lundberg denn...@apache.org wrote:

 On 2011-01-07 17:14, Gordon Cody wrote:
  Hello List
 
  Svn repositories allow for access permissions to be set at the directory
  level.
 
  Maven seems to expect that developers have access to the entire
 repository.

 What makes you think so?

 I use Maven against an SVN repo where I do not have read access to the
 entire repo. There were some problems at first, but those were due to a
 bug in the Subversion client. After I upgraded to Subversion 1.6.12 (I
 think, I'm not on that machine right now), things have worked smoothly.

  Is there a way to reconcile these differences such that some people (for
  example
  junior, qa or non technical people have access only to certain portions
 of
  the repo?
 
  Regards, Gord
  gc...@zafinlabs.com
 


 --
 Dennis Lundberg

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




Re: trouble with checkstyle

2010-08-06 Thread Gordon Cody
Hello Dennis

 Thanks for the link.
It does sound like that error. Pretty crippling (imo).

I found and installed maven-checkstyle-plugin-2.4.jar
and installed it in my artifactory. It took a while to find
one with valid META-INF\maven\plugin.xml.  Same results.

My suspicion is that if I upgraded from maven2.0.9 this problem
would disappear but that is not an option at this time.

Checkstyle 2.5 does work with my checkstyle.xml when configured
within each of my subprojects. So that is what I will be doing for now.

Thanks, Gord


trouble with checkstyle

2010-08-05 Thread Gordon Cody
Hello List

checkstyle is not using my configuration (specifiied in pom). It seems to
insist on
picking up config/sun_checks.xml no matter what i try to do. Using
maven2.0.9
and checkstyle2.5. My project is setup like the multi-module example
project.

In my parent pom I have added to build section.

  plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-checkstyle-plugin/artifactId
  version2.5/version
  dependencies
dependency
  groupIdcom.zafinlabs.mirevenue/groupId
  artifactIdbuild-tools/artifactId
  version${project.version}/version
/dependency
  /dependencies
/plugin

also in parent pom i added reporting section:
  reporting
plugins
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-checkstyle-plugin/artifactId
version2.5/version
configuration
  configLocationmirevenue/zafin_checks.xml/configLocation
  headerLocationmirevenue/LICENSE.txt/headerLocation
/configuration
  /plugin
/plugins
  /reporting
When I do clean:install I see the build-tools.x.y.jar in my local repo with
mirevenue/zafin_checks.xml and license.txt
When I do checkstyle:checkstyle -X I see the following:
[DEBUG] Adding the outputDirectory
file:/C:/spaces/zafin/mirevenue/miArchival/target/classes/ to the Checkstyle
class path
[DEBUG] request.getConfigLocation() config/sun_checks.xml
[DEBUG] The resource 'config/sun_checks.xml' was found as
jar:file:/C:/Documents and
Settings/test/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.5/maven-checkstyle-plugin-2.5.jar!/config/sun_checks.xml.
[DEBUG] headerLocation LICENSE.txt
[DEBUG] The resource 'LICENSE.txt' was found as jar:file:/C:/Documents and
Settings/test/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.5/maven-checkstyle-plugin-2.5.jar!/LICENSE.txt.
It is pulling the files it will use from maven-checkstyle-plugin-2.5.jar
instead of the ones I specify?
Any/all suggestions welcome.

Regards ,Gord


how to get pom updated during mvn release when sub-project is not part of normal build

2010-07-30 Thread Gordon Cody
Hello List

I have a multimodule project similar to the following:

toplevel
  pom.xml
  modA
 pom.xml
  modB
 pom.xml
  modC
 pom.xml

Modules A  B are specified explicitly in the toplevel pom. Module C is not.
It is only to be run when required and is done stand-alone.

When I do mvn release, the toplevel pom and the poms in modA and modB
all get updated with new version as expected but modC does not. Is there
a way to get the normal build to skip modC but get mv release to also update
the pom in modC ?

Thanks for any help
Gord
gc...@zafinlabs.com


mvn and amazon cloud

2010-07-20 Thread Gordon Cody
 Hello

Has anyone succesfully used maven preferably with svn (and either nexus or
artifiactory) within Amazon cloud.
Any useful tips to share?

Regards, Gord Cody
gc...@zafinlabs.com


Re: mvn and amazon cloud

2010-07-20 Thread Gordon Cody
hi
I'm interested in both actually. apologies for being vague.  regards gord

On Jul 20, 2010 4:59 PM, Wayne Fay wayne...@gmail.com wrote:

 Has anyone succesfully used maven preferably with svn (and either nexus or
 artifiactory) within ...
What exactly are you asking about? Building code in an EC2 instance?
Or running a Nexus/Artifactory/etc MRM instance in EC2? Or what??

I would also guess the guys on the Hudson list might have more
relevant experiences to discuss.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


Anyone have experience using maven with Aldon Lifecycle Manager

2010-05-19 Thread Gordon Cody
Has anyone on the list had to integrate maven with the
Aldon Lifecycle Manager ? Any experiences to share ?

-Regards
Gord Cody


version number without . component

2010-02-17 Thread Gordon Cody
Is it possible/reasonable to have a version number be simply
a single number?  e.g. 42-SNAPSHOT. Released version would
be 42 and next snapshot would be 43-SNAPSHOT or is the .
component a requirement?

Thanks  Regards Gord
gc...@zafinlabs.com

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: version number without . component

2010-02-17 Thread Gordon Cody
Thanks for the quick reply.

-Gord


 Is it possible/reasonable to have a version number be simply
 a single number?  e.g. 42-SNAPSHOT. Released version would
 be 42 and next snapshot would be 43-SNAPSHOT or is the .
 component a requirement?

 http://www.jarvana.com/jarvana/search?search_type=projectproject=maven-
 parent


 - Jörg


 -
 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



Re: Broken by design

2009-08-14 Thread Gordon Cody
Download from the internet was one of my biggest fear as well
as versions of underying poms/jars could change which would affect
reproducibilty. Additiionally, download from internet could mean you
might not be able to build at all if some external site cound not be
reached or someone else released a bad version of something.

Happily, with a locally maintained artifacory which is configured to
not automatically look for newer versions we do not have these
types of problems (any more).

Regards, Gord

On Fri, Aug 14, 2009 at 1:26 PM, herve.bout...@free.fr wrote:
 I must admit the download the internet effect is true: everybody can see it 
 when  running Maven for the first time on a computer.
 Is that really a problem? IMHO no:
 - for personal use, this is done only once (and my ADSL line is fine)
 - for corporate use, a repository manager is really welcome, yes

 The most problematic thing in this post is build reproducibility: yes, build 
 reproducibility is crucial, Maven team knows it.
 Maven builds are reproducible.

 But back in '2007: people discovered that build reproducibility was not free, 
 since you had to define a version in your pom for *every* plugin, even those 
 that you even don't imagine it's really defined in a plugin 
 (maven-clean-plugin, for example). The myths of a 5-ligns pom.xml being 
 sufficient, or auto-update of plugins being a kewl feature, were broken ;)
 Yes, this was learned the hard way by many people at that time...

 Later, in Maven 2.0.9, default plugins versions were added in Maven core, so 
 that even a 5-ligns pom.xml gives a reproducible build: if you stick with a 
 precise Maven version, you'll get the same build. It's not the best way of 
 ensuring reproducible build, explicitely defining your plugin version is 
 still better, but it works.
 For more information, see [1] Maven 2.0.9 release notes.


 HTH

 Hervé


 [1] http://maven.apache.org/release-notes-older.html

 - Mail Original -
 De: Todd Thiessen thies...@nortel.com
 À: Todd Thiessen thies...@nortel.com, Maven Users List 
 users@maven.apache.org
 Envoyé: Vendredi 14 Août 2009 14h55:57 GMT +01:00 Amsterdam / Berlin / Berne 
 / Rome / Stockholm / Vienne
 Objet: RE: Broken by design



 We have had some problems with build reproduciblity though.
 But it was because of downloading artifacts.

 Sorry... I meant so say here... It was NOT because of downloading
 artifacts...

 Bah. Friday morning... Brain is still not in gear ;-).

 -
 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



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



strange err during release:prepare

2009-06-05 Thread Gordon Cody
Hello All

We are having trouble running mvn release:prepare on a multimodule projects
The end result is maven aborting the release with its usually helpful
error message
about a missing artifact. The -DdryRun=true option passes of course.

This module is set up like all of the others which have no problems from what
I can tell. The one thing that I did notice is a slight difference in
the maven output
as shown below. Notice there is no ignoring artifact version message
for the module
with the problem, so my question is what would cause this slight
difference to appear
in the output.We are using maven 2.0.9.

[INFO] Updating FeeManagementContainer to 4.15.1
[INFO] Ignoring artifact version update for expression: ${project.version}
[INFO] Updating CloseAccountWorkflow to 4.15.1
[INFO] Ignoring artifact version update for expression: ${project.version}
[INFO] Updating WorkflowUIContainer to 4.15.1
[INFO] Updating CancelWithholdFeesContainer to 4.15.1
[INFO] Ignoring artifact version update for expression: ${project.version}

Any/all help appreciated as this has us stumped.

Regards, Gord

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: SNAPSHOT version question

2009-06-01 Thread Gordon Cody
This question was asked/answered on Apr30.

The person who answered said Use -SNAPSHOT

Some plugins are more picky than others, so use the standard and spare
yourself some pain later.

The artifact, when it leaves your premises should be a released version,
so it should not have the SNAPSHOT suffix (with either dash or dot) anyway.

Regards, Gord

On Mon, Jun 1, 2009 at 11:39 AM, solo1970
sonia.lodoviche...@ericsson.com wrote:

 Hello All,

 Need your expertise to tell me if anyone sees an issue in using .SNAPSHOT
 instead of -SNAPSHOT in an artifact version.  (The reason is because the
 artifact name has to have a minimum amount of '-').

 Example:

 1.0.0.SNAPSHOT

 I'd appreciate feedback

 Sonia
 --
 View this message in context: 
 http://www.nabble.com/SNAPSHOT-version-question-tp23817013p23817013.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


 -
 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



Re: Maven inconsistent build with flexbuilder

2009-05-07 Thread Gordon Cody
Hi Jeff

Its actually much uglier than that in my opinion. In builds done a few seconds
apart there are not just a few bytes that show as different but large chunks of
the swf. I have even seen it generate files that are different in size
(by 1 byte)
which really surprised me.


Regards, Gord

On Thu, May 7, 2009 at 9:06 AM, Jeff MAURY jeffma...@gmail.com wrote:
 Having played with flex-mojos, I remember that the MXML Flex compiler seems
 to put the current date in the generated SWF and it may be binary encoded so
 a simple diff will not clearly expose the difference.

 Regards
 Jeff MAURY

 2009/4/30 Nick Stolwijk nick.stolw...@gmail.com

 Ah, those swf files were generated. :) I thought those came from your SVN.

 Nick Stolwijk
 ~Java Developer~

 Iprofs BV.
 Claus Sluterweg 125
 2012 WS Haarlem
 www.iprofs.nl



 On Wed, Apr 29, 2009 at 10:14 PM, Gordon Cody gc...@zafinlabs.com wrote:
  Upon further investigation me thinks this is a flex issue.
 
  mxmlc x.mxml
 
  twice in a row is generating different swf files
  i have a support call open with them now
 
  Will let you know what I find out.
 
  Thanks for your time Nick
 
  Regards, Gord
 
 
  On Wed, Apr 29, 2009 at 4:05 PM, Nick Stolwijk nick.stolw...@gmail.com
 wrote:
  Are the differences already present between the original source
  (src/main/resources/ or src/main/webapp) and the files under /target
  (whether in /target/classes or in /target/war)?
 
  With regards,
 
  Nick Stolwijk
  ~Java Developer~
 
  Iprofs BV.
  Claus Sluterweg 125
  2012 WS Haarlem
  www.iprofs.nl
 
 
 
  On Wed, Apr 29, 2009 at 10:02 PM, Gordon Cody gc...@zafinlabs.com
 wrote:
  I dont see anything like that in this project. Other projects unrelated
 to flex
  do use filtering.
 
  -Gord
 
  On Wed, Apr 29, 2009 at 3:51 PM, Nick Stolwijk 
 nick.stolw...@gmail.com wrote:
  Could it be that there is some resource filtering going on? [1]
 
  [1]
 http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
 
  Hth,
 
  Nick Stolwijk
  ~Java Developer~
 
  Iprofs BV.
  Claus Sluterweg 125
  2012 WS Haarlem
  www.iprofs.nl
 
 
 
  On Wed, Apr 29, 2009 at 9:38 PM, Gordon Cody gc...@zafinlabs.com
 wrote:
  Hi Nick
  On Wed, Apr 29, 2009 at 3:21 PM, Nick Stolwijk 
 nick.stolw...@gmail.com wrote:
  When I compare the 2 wars, I see  that the swf files are different
 in the 2 versions.
  What do you mean by different?
 
  When I do a byte by byte comparison large chunks of the files show up
  as different
  not just the occasional 4 bytes or even a date string.
 
  As swf files are binary it is extremely difficult to determine if
 the only difference between the 2 is
  timestamps.
  No, it is not. Just compare their checksums (md5). Maven copies the
  resources to /target before war'ing them, so the timestamps could be
  different.
 
  Another cause may be that due to svn:keywords and properties the
 files
  indeed are different. Do you have svn:keywords on your binary files?
 
  No we are not using svn:keywords , but a good point that I will keep
 in mind.
 
  Did you do a new checkout?
  Even if there were svn:keywords those fields would still have been
 the same
  in 2 sequential builds since I did not check out the code again.
 
  Regards Gord
 
 
  With regards,
 
  Nick Stolwijk
  ~Java Developer~
 
  Iprofs BV.
  Claus Sluterweg 125
  2012 WS Haarlem
  www.iprofs.nl
 
 
 
  On Wed, Apr 29, 2009 at 9:14 PM, Gordon Cody gc...@zafinlabs.com
 wrote:
  When I compare the 2 wars, I see  that the swf files are different
 in
  the 2 versions.
 
 
 -
  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
 
 
 
  -
  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
 
 
 
  -
  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
 
 

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




 --
 La mélancolie c’est communiste

Re: How to specify SCM username/password for release plugin?

2009-05-04 Thread Gordon Cody
(with appropriate substitutions of course) In our topmost pom for the
project we use:

  scm

developerConnectionscm:svn:https://svnhost/svnrepo/trunk/developerConnection
  /scm

and in the settings.xml (of those allowed to do releases) we put both
server entries:

  servers
server
idlibs-releases/id
usernamethereleaseuser/username
passwordthereleasepassword/password
/server
server
idlibs-snapshots/id
usernamethedeveloperuser/username
passwordthedeveloperpassword/password
/server
  /servers

Regards,
Gord Cody

On Mon, May 4, 2009 at 5:46 AM, Baptiste MATHUS m...@batmat.net wrote:
 Hi,

 In the documentation of the mojo (btw, you didn't say which goal you were
 speaking) of the release:prepare for example:

 http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html

 username/password.

 Cheers.

 2009/5/1 David Hoffer dhoff...@gmail.com

 How can I specify the username/password to be used by the release plugin in
 the settings.xml file (or other system approach)?  Normally this is set in
 the settings.xml and refereed to elsewhere by it's id but how is this
 refereed by the SCM?

 -Dave




 --
 Baptiste Batmat MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: how to not deploy sources.jar to artifactory

2009-05-01 Thread Gordon Cody
Exactly what I wanted to (not) see.

Thanks again Wendy and Todd too

Regards, Gord

On Wed, Apr 29, 2009 at 5:26 PM, Wendy Smoak wsm...@gmail.com wrote:
 On Wed, Apr 29, 2009 at 1:23 PM, Gordon Cody gc...@zafinlabs.com wrote:
 I know I read this (on someones blog I think) but did not realise I would
 need to care until recently and now I cant find how to do this.

 The requirement is to not deploy sources.jar to the artifactory when
 we do mvn release:perform

 Don't activate the 'release' profile during your release -- that's
 what has the source and javadoc jars configured.

 mvn release:perform ... -DuseReleaseProfile=false

 http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html

 --
 Wendy

 -
 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



Re: how to not deploy sources.jar to artifactory

2009-04-30 Thread Gordon Cody
your efforts were appreciated

Gord Cody

On Thu, Apr 30, 2009 at 9:03 AM, Todd Thiessen thies...@nortel.com wrote:
 haha sorry for my long winded reply. I saw the initial question and
 didn't read all the discussions in between ;-). Glad to hear to go it
 resovled.

 ---
 Todd Thiessen


 -Original Message-
 From: Gordon Cody [mailto:gc...@zafinlabs.com]
 Sent: Wednesday, April 29, 2009 5:43 PM
 To: Maven Users List
 Subject: Re: how to not deploy sources.jar to artifactory

 Thanks Wendy.

 We have to do a release in a couple of days so I wont be able
 to verify this till then and of course once I knew what to
 look for I found it in the parameter doc for the release plugin.

 Have a great day, Gord

 On Wed, Apr 29, 2009 at 5:26 PM, Wendy Smoak wsm...@gmail.com wrote:
  On Wed, Apr 29, 2009 at 1:23 PM, Gordon Cody
 gc...@zafinlabs.com wrote:
  I know I read this (on someones blog I think) but did not
 realise I
  would need to care until recently and now I cant find how
 to do this.
 
  The requirement is to not deploy sources.jar to the
 artifactory when
  we do mvn release:perform
 
  Don't activate the 'release' profile during your release -- that's
  what has the source and javadoc jars configured.
 
  mvn release:perform ... -DuseReleaseProfile=false
 
 
 http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html
 
  --
  Wendy
 
 
 -
  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



 -
 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



Maven inconsistent build with flexbuilder

2009-04-29 Thread Gordon Cody
Hello

Working in release mgmt, one of my many jobs is to ensure that we can reliably
reproduce what will be delivered to a customer.

We are using flexbuilder3 in a windows/maven development environment.
I check out the code from svn and run mvn clean install. This generates
a war file that contains swf files among other things.
I move that war file aside and run mvn clean install a second time.

When I compare the 2 wars, I see  that the swf files are different in
the 2 versions.
As swf files are binary it is extremely difficult to determine if the
only difference
between the 2 is timestamps.

Please, what can I do to eliminate these differences?

Thanks in advance for any help,
-Gord

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Maven inconsistent build with flexbuilder

2009-04-29 Thread Gordon Cody
Hi Nick
On Wed, Apr 29, 2009 at 3:21 PM, Nick Stolwijk nick.stolw...@gmail.com wrote:
 When I compare the 2 wars, I see  that the swf files are different in the 2 
 versions.
 What do you mean by different?

When I do a byte by byte comparison large chunks of the files show up
as different
not just the occasional 4 bytes or even a date string.

 As swf files are binary it is extremely difficult to determine if the only 
 difference between the 2 is
 timestamps.
 No, it is not. Just compare their checksums (md5). Maven copies the
 resources to /target before war'ing them, so the timestamps could be
 different.

 Another cause may be that due to svn:keywords and properties the files
 indeed are different. Do you have svn:keywords on your binary files?

No we are not using svn:keywords , but a good point that I will keep in mind.

 Did you do a new checkout?
Even if there were svn:keywords those fields would still have been the same
in 2 sequential builds since I did not check out the code again.

Regards Gord


 With regards,

 Nick Stolwijk
 ~Java Developer~

 Iprofs BV.
 Claus Sluterweg 125
 2012 WS Haarlem
 www.iprofs.nl



 On Wed, Apr 29, 2009 at 9:14 PM, Gordon Cody gc...@zafinlabs.com wrote:
 When I compare the 2 wars, I see  that the swf files are different in
 the 2 versions.

 -
 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



Re: Maven inconsistent build with flexbuilder

2009-04-29 Thread Gordon Cody
I dont see anything like that in this project. Other projects unrelated to flex
do use filtering.

-Gord

On Wed, Apr 29, 2009 at 3:51 PM, Nick Stolwijk nick.stolw...@gmail.com wrote:
 Could it be that there is some resource filtering going on? [1]

 [1] 
 http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html

 Hth,

 Nick Stolwijk
 ~Java Developer~

 Iprofs BV.
 Claus Sluterweg 125
 2012 WS Haarlem
 www.iprofs.nl



 On Wed, Apr 29, 2009 at 9:38 PM, Gordon Cody gc...@zafinlabs.com wrote:
 Hi Nick
 On Wed, Apr 29, 2009 at 3:21 PM, Nick Stolwijk nick.stolw...@gmail.com 
 wrote:
 When I compare the 2 wars, I see  that the swf files are different in the 
 2 versions.
 What do you mean by different?

 When I do a byte by byte comparison large chunks of the files show up
 as different
 not just the occasional 4 bytes or even a date string.

 As swf files are binary it is extremely difficult to determine if the only 
 difference between the 2 is
 timestamps.
 No, it is not. Just compare their checksums (md5). Maven copies the
 resources to /target before war'ing them, so the timestamps could be
 different.

 Another cause may be that due to svn:keywords and properties the files
 indeed are different. Do you have svn:keywords on your binary files?

 No we are not using svn:keywords , but a good point that I will keep in mind.

 Did you do a new checkout?
 Even if there were svn:keywords those fields would still have been the same
 in 2 sequential builds since I did not check out the code again.

 Regards Gord


 With regards,

 Nick Stolwijk
 ~Java Developer~

 Iprofs BV.
 Claus Sluterweg 125
 2012 WS Haarlem
 www.iprofs.nl



 On Wed, Apr 29, 2009 at 9:14 PM, Gordon Cody gc...@zafinlabs.com wrote:
 When I compare the 2 wars, I see  that the swf files are different in
 the 2 versions.

 -
 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



 -
 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



Re: Maven inconsistent build with flexbuilder

2009-04-29 Thread Gordon Cody
Upon further investigation me thinks this is a flex issue.

mxmlc x.mxml

twice in a row is generating different swf files
i have a support call open with them now

Will let you know what I find out.

Thanks for your time Nick

Regards, Gord


On Wed, Apr 29, 2009 at 4:05 PM, Nick Stolwijk nick.stolw...@gmail.com wrote:
 Are the differences already present between the original source
 (src/main/resources/ or src/main/webapp) and the files under /target
 (whether in /target/classes or in /target/war)?

 With regards,

 Nick Stolwijk
 ~Java Developer~

 Iprofs BV.
 Claus Sluterweg 125
 2012 WS Haarlem
 www.iprofs.nl



 On Wed, Apr 29, 2009 at 10:02 PM, Gordon Cody gc...@zafinlabs.com wrote:
 I dont see anything like that in this project. Other projects unrelated to 
 flex
 do use filtering.

 -Gord

 On Wed, Apr 29, 2009 at 3:51 PM, Nick Stolwijk nick.stolw...@gmail.com 
 wrote:
 Could it be that there is some resource filtering going on? [1]

 [1] 
 http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html

 Hth,

 Nick Stolwijk
 ~Java Developer~

 Iprofs BV.
 Claus Sluterweg 125
 2012 WS Haarlem
 www.iprofs.nl



 On Wed, Apr 29, 2009 at 9:38 PM, Gordon Cody gc...@zafinlabs.com wrote:
 Hi Nick
 On Wed, Apr 29, 2009 at 3:21 PM, Nick Stolwijk nick.stolw...@gmail.com 
 wrote:
 When I compare the 2 wars, I see  that the swf files are different in 
 the 2 versions.
 What do you mean by different?

 When I do a byte by byte comparison large chunks of the files show up
 as different
 not just the occasional 4 bytes or even a date string.

 As swf files are binary it is extremely difficult to determine if the 
 only difference between the 2 is
 timestamps.
 No, it is not. Just compare their checksums (md5). Maven copies the
 resources to /target before war'ing them, so the timestamps could be
 different.

 Another cause may be that due to svn:keywords and properties the files
 indeed are different. Do you have svn:keywords on your binary files?

 No we are not using svn:keywords , but a good point that I will keep in 
 mind.

 Did you do a new checkout?
 Even if there were svn:keywords those fields would still have been the same
 in 2 sequential builds since I did not check out the code again.

 Regards Gord


 With regards,

 Nick Stolwijk
 ~Java Developer~

 Iprofs BV.
 Claus Sluterweg 125
 2012 WS Haarlem
 www.iprofs.nl



 On Wed, Apr 29, 2009 at 9:14 PM, Gordon Cody gc...@zafinlabs.com wrote:
 When I compare the 2 wars, I see  that the swf files are different in
 the 2 versions.

 -
 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



 -
 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



 -
 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



how to not deploy sources.jar to artifactory

2009-04-29 Thread Gordon Cody
I know I read this (on someones blog I think) but did not realise I would
need to care until recently and now I cant find how to do this.

The requirement is to not deploy sources.jar to the artifactory when
we do mvn release:perform

Thanks in advance for any/all help

Regards, Gord

-- Forwarded message --
From: Gordon Cody gc...@zafinlabs.com
Date: Wed, Apr 29, 2009 at 3:14 PM
Subject: Maven inconsistent build with flexbuilder
To: Maven Users List users@maven.apache.org


Hello

Working in release mgmt, one of my many jobs is to ensure that we can reliably
reproduce what will be delivered to a customer.

We are using flexbuilder3 in a windows/maven development environment.
I check out the code from svn and run mvn clean install. This generates
a war file that contains swf files among other things.
I move that war file aside and run mvn clean install a second time.

When I compare the 2 wars, I see  that the swf files are different in
the 2 versions.
As swf files are binary it is extremely difficult to determine if the
only difference
between the 2 is timestamps.

Please, what can I do to eliminate these differences?

Thanks in advance for any help,
-Gord

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: how to not deploy sources.jar to artifactory

2009-04-29 Thread Gordon Cody
Hello Todd

My apologies as I am just getting to know mvn.

From my searching, we do not reference the maven-source-plugin
directly anywhere.
I have located the reference to the maven-release-plugin. It is in our
topmost pom.xml
and contains only:
build
  plugins
plugin
  groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
configuration
  arguments-Dmaven.test.skip=true/arguments
/configuration
 /plugin
  /plugins
/build

If I understand what you are saying I need to explicitly invoke the
maven-source-plugin
but configure it so that it does not have specify any goals. Is that correct?

Appreciating your patience, Gord


On Wed, Apr 29, 2009 at 4:28 PM, Todd Thiessen thies...@nortel.com wrote:
 You can override the release-profile profile of the super pom. Define this 
 profile yourself and ensure that the maven-source-plugin does not define an 
 execution to build a sources jar.

 ---
 Todd Thiessen


 -Original Message-
 From: Gordon Cody [mailto:gc...@zafinlabs.com]
 Sent: Wednesday, April 29, 2009 4:23 PM
 To: users@maven.apache.org
 Subject: how to not deploy sources.jar to artifactory

 I know I read this (on someones blog I think) but did not
 realise I would need to care until recently and now I cant
 find how to do this.

 The requirement is to not deploy sources.jar to the
 artifactory when we do mvn release:perform

 Thanks in advance for any/all help

 Regards, Gord

 -- Forwarded message --
 From: Gordon Cody gc...@zafinlabs.com
 Date: Wed, Apr 29, 2009 at 3:14 PM
 Subject: Maven inconsistent build with flexbuilder
 To: Maven Users List users@maven.apache.org


 Hello

 Working in release mgmt, one of my many jobs is to ensure
 that we can reliably reproduce what will be delivered to a customer.

 We are using flexbuilder3 in a windows/maven development environment.
 I check out the code from svn and run mvn clean install. This
 generates a war file that contains swf files among other things.
 I move that war file aside and run mvn clean install a second time.

 When I compare the 2 wars, I see  that the swf files are
 different in the 2 versions.
 As swf files are binary it is extremely difficult to
 determine if the only difference between the 2 is timestamps.

 Please, what can I do to eliminate these differences?

 Thanks in advance for any help,
 -Gord

 -
 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



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: how to not deploy sources.jar to artifactory

2009-04-29 Thread Gordon Cody
Thanks Wendy.

We have to do a release in a couple of days so I wont be able to
verify this till
then and of course once I knew what to look for I found it in the parameter doc
for the release plugin.

Have a great day, Gord

On Wed, Apr 29, 2009 at 5:26 PM, Wendy Smoak wsm...@gmail.com wrote:
 On Wed, Apr 29, 2009 at 1:23 PM, Gordon Cody gc...@zafinlabs.com wrote:
 I know I read this (on someones blog I think) but did not realise I would
 need to care until recently and now I cant find how to do this.

 The requirement is to not deploy sources.jar to the artifactory when
 we do mvn release:perform

 Don't activate the 'release' profile during your release -- that's
 what has the source and javadoc jars configured.

 mvn release:perform ... -DuseReleaseProfile=false

 http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html

 --
 Wendy

 -
 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