Re: Using artifacts as resources in other projects.
Wiadomość napisana przez Jeff MAURY w dniu 2 kwi 2012, o godz. 21:02: You should probably use the maven assembly plugin Thanks. I'll look on this plugin when come back to that project. Best regards, Mariusz Pluciński
Passive Mode
Hi, How I can do for set Passive mode to false with maven3 Un Saludo, Domingo José González Cabrera Coordinador del área de Nuevas Tecnologías doming...@gmrcanarias.com mailto:doming...@gmrcanarias.com www.gmrcanarias.com http://www.gmrcanarias.com/ C/ Subida al Mayorazgo 26, portal B Planta 2 - Polígono Industrial El Mayorazgo 38108 Santa Cruz de Tenerife Tel: 902 377 777 Fax: 922 236 109
ftp-wagon
Hi, how set passivemode = false. My pom.xml
build
sourceDirectory${basedir}/src/sourceDirectory
outputDirectory${basedir}/WebRoot/WEB-INF/classes/outputDirectory
resources
resource
directory${basedir}/src/directory
excludes
exclude**/*.java/exclude
/excludes
/resource
/resources
!-- Extension FTP del plug in wagon --
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-ftp/artifactId
version2.2/version
/extension
/extensions
plugins
plugin
artifactIdmaven-war-plugin/artifactId
configuration
webappDirectory${basedir}/WebRoot/webappDirectory
warSourceDirectory${basedir}/WebRoot/warSourceDirectory
/configuration
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdwagon-maven-plugin/artifactId
!-- Contains unique execution declarations for CSS
files, layout images
and war file. --
executions
!-- Declaration for copying CSS files via FTP --
execution
idupload/id
!-- Describes the lifecycle phase when the
plugin's goals are being
executed. --
phaseinstall/phase
!-- Describes the goals are executed in the
specified lifecycle phase. --
goals
goalupload/goal
/goals
configuration
!-- Describes the local directory,
which contents are copied. --
fromDir${webapp.local.dir}/fromDir
!-- Describes the included files. --
includes*/includes
!-- Describes the url of the remote
FTP server. --
url${webapp.remote.url}/url
!-- Describes the remote directory,
where the contents of the local
directory are copied. --
toDir${webapp.remote.dir}/toDir
!-- Describes the server id, which is
used to fetch the used credentials
from settings.xml. --
serverId${webapp.remote.server.id}/serverId
/configuration
/execution
/executions
/plugin
/plugins
/build
Un Saludo,
Domingo José González Cabrera
Coordinador del área de Nuevas Tecnologías
doming...@gmrcanarias.com mailto:doming...@gmrcanarias.com
www.gmrcanarias.com http://www.gmrcanarias.com/
C/ Subida al Mayorazgo 26, portal B
Planta 2 - Polígono Industrial El Mayorazgo
38108 Santa Cruz de Tenerife
Tel: 902 377 777 Fax: 922 236 109
No overwrite
Here is a dev scenario : We are using maven 3 + artifactory + microst TFS server We dont want to over write an existing version of an artifact in our company repo , so the the consumers of artifacts should not be surprised all the sudden when producers update artifact. Now this can simply be done by removing delete permissions in artifactory but then that causes another problem. In multi module maven project if one module changes then either dev need to modify version on all artifacts ( which doesnt make sense ) or then need to modify individual pom and publish only the artifact that is changes * which again is not manageable ) So need some advice on how this can be handled ? I have couple of thoughts : - Before running mvn command , write some thing custom to go through all pom's and query artifactory is version of artifact exist. if yes then dont compile. Basically compile only artifacts who version doesnt exist in artifactory using mvn -pl - Try Jenkins , I know jenkins is aware of modules in project , but not sure if it intelligent enough to compile only those which are changed ? Please advice -Raj
