I have situation when I can use attachements, but the team wants some backward compatibility with the previous system where we explicitly placed that svnstatus information into META-INF. I also see this as a stupid idea, but now we have applications which reads that metainformation to help the support team. Right now I am fighting to use maven. I know that with maven several things gets the right place, but until all the users gets the feeling, some compromises I have to leave it open.
Definitively I'll use profiles to switch between.... Thanks! Tibor ________________________________________ Feladó: Brett Porter [EMAIL PROTECTED] This is by design to prevent the artifacts in the local repository being different from the ones in the remote repository :) Does it make more sense to deploy the results as a separate attachment, rather than putting it inside META-INF? Otherwise, I would suggest using a profile to enable it when deploying. It makes deploying a longer command, but it sounds like this is your less frequent use case. - Brett 2008/9/30 Tibor Kiss <[EMAIL PROTECTED]>: > Hi, > > My usecase is the following. > > The team want to enforce a svn status check against source codes before > deploying into repository. But not for install! > I wrote a maven plugin which does the checking. The only missing piece is > that until now I just solved the problem by a configuration parameter > "<skipCheck>false</skipCheck>" which tells that now I don't want to check svn > status, let me install as is. > Unfortunately I cannot just attach the Mojo to "deploy" phase. I have to > attach to "package" phase, because I have to save the result within the > META-INF directory. > > It's a bit inconvenient to always switch this parameter by editing the > configuration. I would like to know if the deploy phase is really running or > not. > > Tibor > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
