[
http://jira.amdatu.org/jira/browse/AMDATUAUTH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn resolved AMDATUAUTH-57.
----------------------------------------------
Resolution: Fixed
Moved the copy to deploy dir stuff to the "deploy" profile. Also fixed the
check that verifies if the amdatu.deploy.directory property is set. If not, a
warning message is displayed instead of creating the bogus
"${amdatu.deploy.directory}" directory.
Finally, removed the config copy logic as it didn't work from the root
directory (as it used relative paths) and was not really necessary anyway.
> Antrun stuff creates rogue dirs if prop not set
> -----------------------------------------------
>
> Key: AMDATUAUTH-57
> URL: http://jira.amdatu.org/jira/browse/AMDATUAUTH-57
> Project: Amdatu Auth
> Issue Type: Bug
> Components: Project infrastructure
> Reporter: Bram de Kruijff
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.2.0
>
>
> The main pom contains some ant stuff to deploy jars to a local dir. It
> depends on ${amdatu.deploy.directory} to be set but checks it wrong. As a
> result dirs name "${amdatu.deploy.directory}" gets created all over the
> place. Either fix the ant logic or, even better, use a maven profile. The
> latter can use either property based activation or just explicitly named
> (like -P deploy-local or something).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
