You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Troy Bull <tr...@gmail.com> on 2009/03/27 15:08:40 UTC

Modify file inside war

Greetings,

I am in charge of deploying applications for my company.  I am given war
files by developers or cruise control builds.  These builds some times have
1 extra line the META-INF/Manifest.mf file.

Is there a way with ant I can remove this line from this file?

Basically as I see it the worst case :
I need to explode the war file
Check if this line exists in the Manifest.mf,
if the line exists remove it
rebuild the war file with the new manifest

is there an easier way?  Is this way possible?  If so what "tasks" would I
use?

Thanks in advance

Troy

RE: Modify file inside war

Posted by Rémon van Gijn <r....@portbase.com>.
How about fixing the generation?

Why ever would it matter if there is an extra line in the .mf file?

Rémon

 


-----Original Message-----
From: Troy Bull [mailto:troy.bull@gmail.com] 
Sent: vrijdag 27 maart 2009 15:09
To: user@ant.apache.org
Subject: Modify file inside war

Greetings,

I am in charge of deploying applications for my company.  I am given war
files by developers or cruise control builds.  These builds some times have
1 extra line the META-INF/Manifest.mf file.

Is there a way with ant I can remove this line from this file?

Basically as I see it the worst case :
I need to explode the war file
Check if this line exists in the Manifest.mf,
if the line exists remove it
rebuild the war file with the new manifest

is there an easier way?  Is this way possible?  If so what "tasks" would I
use?

Thanks in advance

Troy

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


RE: Modify file inside war

Posted by Martin Gainty <mg...@hotmail.com>.
Its easier to either 
a)birth out the jsps,java classes,xml configuration file and fix the error or 
b)ensure you hire competent developers..(easier said than done)

As the design grows in complexity evolving into MVC or J2EE 
usually the breakdown is

Front End: JSP/JavaScript guy/gal
MiddleWare: Hibernate/Spring and or Action classes/WebServices guy/gal
Backend: DB guy/gal

and for J2EE
ejb-jar.xml/jca-persistence.xml/data-source.xml and/or Bean configurations guy/gal

You (as BuildManager) need to arbitrate what gets included 
Martin 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung / Disclaimer and confidentiality note 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
This message is confidential and may be privileged. If you are not the intended recipient, we kindly ask you to  please inform the sender. Any unauthorised dissemination or copying hereof is prohibited. This message serves for information purposes only and shall not have any legally binding effect. Given that e-mails can easily be subject to manipulation, we can not accept any liability for the content provided.






> Subject: RE: Modify file inside war
> Date: Fri, 27 Mar 2009 13:17:09 -0700
> From: CJi@pro-unlimited.com
> To: user@ant.apache.org
> 
> Well, sometimes it does happen, such as one group is doing the coding on Window platform and the release work has been done on Unix/Linux. There is very difficult to say whose fault it is. 
> 
> 
> -cji
> 
> 
> -----Original Message-----
> From: David Weintraub [mailto:qazwart@gmail.com] 
> Sent: Friday, March 27, 2009 7:38 AM
> To: Ant Users List
> Subject: Re: Modify file inside war
> 
> Okay: I have a firm belief in the "Finger o' Blame". The idea in
> development is to get the "Finger 'o Blame" pointing at someone else.
> 
> Many times, one group pushes their issues upon another group further
> down the line. This allows the Finger 'o Blame to fall onto that next
> group instead of the first group that caused the issues.
> 
> I've taken over many build/release engineer positions where people
> have told me "I hope you're better than that other idiot we had. He
> couldn't do anything right. Every time we had a release, he couldn't
> get it working in production."
> 
> Then, comes the fun, I start throwing back releases to development
> telling them that the product cannot be released as it stands. I would
> fail a build for things like Warfiles that have bad MANIFEST.MF in
> them. The usual responses would go "Well, the former build/release guy
> use to allow this type of stuff", or "Can't you just fix it? It's an
> easy thing to fix?".
> 
> After a few weeks of this (and helping the developers with their buid
> issues, so their code can be correctly deployed), the whole process
> goes smoother. Our deployments are less error prone. They go smoother.
> Customers are happier. They start believing we are competent
> professionals. We feel better about ourselves. And, it's all because I
> insist that people should be responsible for their problems and not
> push them off on someone else (like me).
> 
> I may not be any more competent than the "idiot" who proceeded me, but
> instead of looking like an idiot because I am trying to fix everyone
> else's problems, I make sure they fix their own issues and not simply
> toss over in my direction.
> 
> The point is, you should not allow developers to hand you over
> defective WAR files and then expect you to fix them. Yes, it's not a
> difficult fix, but then that means it shouldn't be difficult for the
> developers to get them right in the first place.
> 
> Yes, it is possible to use Ant to do this type of task, but Ant is
> really made for producing builds and not a general purpose scripting
> language. I would personally use Perl or Python to go through and fix
> these WAR files instead of Ant.
> 
> Actually, I would personally refuse to fix them and consider them
> undeployable, and make the developers fix their own issues.
> 
> On Fri, Mar 27, 2009 at 10:08 AM, Troy Bull <tr...@gmail.com> wrote:
> > Greetings,
> >
> > I am in charge of deploying applications for my company.  I am given war
> > files by developers or cruise control builds.  These builds some times have
> > 1 extra line the META-INF/Manifest.mf file.
> >
> > Is there a way with ant I can remove this line from this file?
> >
> > Basically as I see it the worst case :
> > I need to explode the war file
> > Check if this line exists in the Manifest.mf,
> > if the line exists remove it
> > rebuild the war file with the new manifest
> >
> > is there an easier way?  Is this way possible?  If so what "tasks" would I
> > use?
> >
> > Thanks in advance
> >
> > Troy
> >
> 
> 
> 
> -- 
> --
> David Weintraub
> qazwart@gmail.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
> 

_________________________________________________________________
Hotmail® is up to 70% faster. Now good news travels really fast.
http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009

RE: Modify file inside war

Posted by Chun Ji <CJ...@pro-unlimited.com>.
Well, sometimes it does happen, such as one group is doing the coding on Window platform and the release work has been done on Unix/Linux. There is very difficult to say whose fault it is. 


-cji


-----Original Message-----
From: David Weintraub [mailto:qazwart@gmail.com] 
Sent: Friday, March 27, 2009 7:38 AM
To: Ant Users List
Subject: Re: Modify file inside war

Okay: I have a firm belief in the "Finger o' Blame". The idea in
development is to get the "Finger 'o Blame" pointing at someone else.

Many times, one group pushes their issues upon another group further
down the line. This allows the Finger 'o Blame to fall onto that next
group instead of the first group that caused the issues.

I've taken over many build/release engineer positions where people
have told me "I hope you're better than that other idiot we had. He
couldn't do anything right. Every time we had a release, he couldn't
get it working in production."

Then, comes the fun, I start throwing back releases to development
telling them that the product cannot be released as it stands. I would
fail a build for things like Warfiles that have bad MANIFEST.MF in
them. The usual responses would go "Well, the former build/release guy
use to allow this type of stuff", or "Can't you just fix it? It's an
easy thing to fix?".

After a few weeks of this (and helping the developers with their buid
issues, so their code can be correctly deployed), the whole process
goes smoother. Our deployments are less error prone. They go smoother.
Customers are happier. They start believing we are competent
professionals. We feel better about ourselves. And, it's all because I
insist that people should be responsible for their problems and not
push them off on someone else (like me).

I may not be any more competent than the "idiot" who proceeded me, but
instead of looking like an idiot because I am trying to fix everyone
else's problems, I make sure they fix their own issues and not simply
toss over in my direction.

The point is, you should not allow developers to hand you over
defective WAR files and then expect you to fix them. Yes, it's not a
difficult fix, but then that means it shouldn't be difficult for the
developers to get them right in the first place.

Yes, it is possible to use Ant to do this type of task, but Ant is
really made for producing builds and not a general purpose scripting
language. I would personally use Perl or Python to go through and fix
these WAR files instead of Ant.

Actually, I would personally refuse to fix them and consider them
undeployable, and make the developers fix their own issues.

On Fri, Mar 27, 2009 at 10:08 AM, Troy Bull <tr...@gmail.com> wrote:
> Greetings,
>
> I am in charge of deploying applications for my company.  I am given war
> files by developers or cruise control builds.  These builds some times have
> 1 extra line the META-INF/Manifest.mf file.
>
> Is there a way with ant I can remove this line from this file?
>
> Basically as I see it the worst case :
> I need to explode the war file
> Check if this line exists in the Manifest.mf,
> if the line exists remove it
> rebuild the war file with the new manifest
>
> is there an easier way?  Is this way possible?  If so what "tasks" would I
> use?
>
> Thanks in advance
>
> Troy
>



-- 
--
David Weintraub
qazwart@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Re: Modify file inside war

Posted by David Weintraub <qa...@gmail.com>.
Okay: I have a firm belief in the "Finger o' Blame". The idea in
development is to get the "Finger 'o Blame" pointing at someone else.

Many times, one group pushes their issues upon another group further
down the line. This allows the Finger 'o Blame to fall onto that next
group instead of the first group that caused the issues.

I've taken over many build/release engineer positions where people
have told me "I hope you're better than that other idiot we had. He
couldn't do anything right. Every time we had a release, he couldn't
get it working in production."

Then, comes the fun, I start throwing back releases to development
telling them that the product cannot be released as it stands. I would
fail a build for things like Warfiles that have bad MANIFEST.MF in
them. The usual responses would go "Well, the former build/release guy
use to allow this type of stuff", or "Can't you just fix it? It's an
easy thing to fix?".

After a few weeks of this (and helping the developers with their buid
issues, so their code can be correctly deployed), the whole process
goes smoother. Our deployments are less error prone. They go smoother.
Customers are happier. They start believing we are competent
professionals. We feel better about ourselves. And, it's all because I
insist that people should be responsible for their problems and not
push them off on someone else (like me).

I may not be any more competent than the "idiot" who proceeded me, but
instead of looking like an idiot because I am trying to fix everyone
else's problems, I make sure they fix their own issues and not simply
toss over in my direction.

The point is, you should not allow developers to hand you over
defective WAR files and then expect you to fix them. Yes, it's not a
difficult fix, but then that means it shouldn't be difficult for the
developers to get them right in the first place.

Yes, it is possible to use Ant to do this type of task, but Ant is
really made for producing builds and not a general purpose scripting
language. I would personally use Perl or Python to go through and fix
these WAR files instead of Ant.

Actually, I would personally refuse to fix them and consider them
undeployable, and make the developers fix their own issues.

On Fri, Mar 27, 2009 at 10:08 AM, Troy Bull <tr...@gmail.com> wrote:
> Greetings,
>
> I am in charge of deploying applications for my company.  I am given war
> files by developers or cruise control builds.  These builds some times have
> 1 extra line the META-INF/Manifest.mf file.
>
> Is there a way with ant I can remove this line from this file?
>
> Basically as I see it the worst case :
> I need to explode the war file
> Check if this line exists in the Manifest.mf,
> if the line exists remove it
> rebuild the war file with the new manifest
>
> is there an easier way?  Is this way possible?  If so what "tasks" would I
> use?
>
> Thanks in advance
>
> Troy
>



-- 
--
David Weintraub
qazwart@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org