Re: Passing system arguments to the forked maven process for release:prepare and release:perform
That sorted it. Here's a link to the complete POM for anyone else who has this
issue as well.
https://github.com/apigee/beanstalk-spring-integration/blob/02926556b51ec24b916a9ea41182c5bc10059609/pom.xml
Thanks again for the help!
--
Todd Nine
On Thursday, July 12, 2012 at 2:43 PM, Stephen Connolly wrote:
yours since you don't control the parent
On 12 July 2012 22:35, Todd Nine tn...@apigee.com (mailto:tn...@apigee.com)
wrote:
Thanks Stephen!
Do I need to do that in the parent pom or in mine?
--
Todd Nine
On Thursday, July 12, 2012 at 2:33 PM, Stephen Connolly wrote:
Override back to ${arguments} -Psonatype-...
On Thursday, 12 July 2012, Todd Nine wrote:
Any idea how to merge the two? I obviously want command line arguments,
putting our S3 creeds into a public repo isn't a very good idea! ;)
--
Todd Nine
On Thursday, July 12, 2012 at 2:14 PM, Ansgar Konermann wrote:
Am 12.07.2012 22:33, schrieb Todd Nine:
Hi all,
I'm attempting to re-package a 3rd party open source project and
create our own custom distribution. I've modified and the source, and
the
repo is available here.
https://github.com/apigee/beanstalk-spring-integration/tree/usergrid
I'm attempting to perform a release, however these properties must
be
present at runtime for testing to work properly.
-DAWS_ACCESS_KEY_ID=[your aws accesskey] -DAWS_SECRET_KEY=[your aws
secret key]
Because this uses sensitive data, I obviously don't want to put
these
properties in the Pom. I've scoured the documentation, but I'm unable
to
find an example of how to do this, and I know I've done it before!
Here is
what I'm attempting, which is failing.
mvn release:prepare release:perform
-Darguments=-DAWS_ACCESS_KEY_ID=[your aws accesskey]
-DAWS_SECRET_KEY=[your aws secret key]
Any help would be greatly appreciated!
Thanks,
This is in your parent pom (org.sonatype.oss:oss-parent:7:pom):
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.1/version
configuration
mavenExecutorIdforked-path/mavenExecutorId
useReleaseProfilefalse/useReleaseProfile
arguments-Psonatype-oss-release/arguments
/configuration
/plugin
/plugins
/pluginManagement
It overrides m-release-plugin's arguments. I suspect this will
override the -Darguments on the command line.
HTH
Ansgar
Passing system arguments to the forked maven process for release:prepare and release:perform
Hi all, I'm attempting to re-package a 3rd party open source project and create our own custom distribution. I've modified and the source, and the repo is available here. https://github.com/apigee/beanstalk-spring-integration/tree/usergrid I'm attempting to perform a release, however these properties must be present at runtime for testing to work properly. -DAWS_ACCESS_KEY_ID=[your aws accesskey] -DAWS_SECRET_KEY=[your aws secret key] Because this uses sensitive data, I obviously don't want to put these properties in the Pom. I've scoured the documentation, but I'm unable to find an example of how to do this, and I know I've done it before! Here is what I'm attempting, which is failing. mvn release:prepare release:perform -Darguments=-DAWS_ACCESS_KEY_ID=[your aws accesskey] -DAWS_SECRET_KEY=[your aws secret key] Any help would be greatly appreciated! Thanks, -- Todd Nine
Re: Passing system arguments to the forked maven process for release:prepare and release:perform
Am 12.07.2012 22:33, schrieb Todd Nine: Hi all, I'm attempting to re-package a 3rd party open source project and create our own custom distribution. I've modified and the source, and the repo is available here. https://github.com/apigee/beanstalk-spring-integration/tree/usergrid I'm attempting to perform a release, however these properties must be present at runtime for testing to work properly. -DAWS_ACCESS_KEY_ID=[your aws accesskey] -DAWS_SECRET_KEY=[your aws secret key] Because this uses sensitive data, I obviously don't want to put these properties in the Pom. I've scoured the documentation, but I'm unable to find an example of how to do this, and I know I've done it before! Here is what I'm attempting, which is failing. mvn release:prepare release:perform -Darguments=-DAWS_ACCESS_KEY_ID=[your aws accesskey] -DAWS_SECRET_KEY=[your aws secret key] Any help would be greatly appreciated! Thanks, This is in your parent pom (org.sonatype.oss:oss-parent:7:pom): pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.1/version configuration mavenExecutorIdforked-path/mavenExecutorId useReleaseProfilefalse/useReleaseProfile arguments-Psonatype-oss-release/arguments /configuration /plugin /plugins /pluginManagement It overrides m-release-plugin's arguments. I suspect this will override the -Darguments on the command line. HTH Ansgar
Re: Passing system arguments to the forked maven process for release:prepare and release:perform
Any idea how to merge the two? I obviously want command line arguments, putting our S3 creeds into a public repo isn't a very good idea! ;) -- Todd Nine On Thursday, July 12, 2012 at 2:14 PM, Ansgar Konermann wrote: Am 12.07.2012 22:33, schrieb Todd Nine: Hi all, I'm attempting to re-package a 3rd party open source project and create our own custom distribution. I've modified and the source, and the repo is available here. https://github.com/apigee/beanstalk-spring-integration/tree/usergrid I'm attempting to perform a release, however these properties must be present at runtime for testing to work properly. -DAWS_ACCESS_KEY_ID=[your aws accesskey] -DAWS_SECRET_KEY=[your aws secret key] Because this uses sensitive data, I obviously don't want to put these properties in the Pom. I've scoured the documentation, but I'm unable to find an example of how to do this, and I know I've done it before! Here is what I'm attempting, which is failing. mvn release:prepare release:perform -Darguments=-DAWS_ACCESS_KEY_ID=[your aws accesskey] -DAWS_SECRET_KEY=[your aws secret key] Any help would be greatly appreciated! Thanks, This is in your parent pom (org.sonatype.oss:oss-parent:7:pom): pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.1/version configuration mavenExecutorIdforked-path/mavenExecutorId useReleaseProfilefalse/useReleaseProfile arguments-Psonatype-oss-release/arguments /configuration /plugin /plugins /pluginManagement It overrides m-release-plugin's arguments. I suspect this will override the -Darguments on the command line. HTH Ansgar
Re: Passing system arguments to the forked maven process for release:prepare and release:perform
Override back to ${arguments} -Psonatype-...
On Thursday, 12 July 2012, Todd Nine wrote:
Any idea how to merge the two? I obviously want command line arguments,
putting our S3 creeds into a public repo isn't a very good idea! ;)
--
Todd Nine
On Thursday, July 12, 2012 at 2:14 PM, Ansgar Konermann wrote:
Am 12.07.2012 22:33, schrieb Todd Nine:
Hi all,
I'm attempting to re-package a 3rd party open source project and
create our own custom distribution. I've modified and the source, and the
repo is available here.
https://github.com/apigee/beanstalk-spring-integration/tree/usergrid
I'm attempting to perform a release, however these properties must be
present at runtime for testing to work properly.
-DAWS_ACCESS_KEY_ID=[your aws accesskey] -DAWS_SECRET_KEY=[your aws
secret key]
Because this uses sensitive data, I obviously don't want to put these
properties in the Pom. I've scoured the documentation, but I'm unable to
find an example of how to do this, and I know I've done it before! Here is
what I'm attempting, which is failing.
mvn release:prepare release:perform
-Darguments=-DAWS_ACCESS_KEY_ID=[your aws accesskey]
-DAWS_SECRET_KEY=[your aws secret key]
Any help would be greatly appreciated!
Thanks,
This is in your parent pom (org.sonatype.oss:oss-parent:7:pom):
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.1/version
configuration
mavenExecutorIdforked-path/mavenExecutorId
useReleaseProfilefalse/useReleaseProfile
arguments-Psonatype-oss-release/arguments
/configuration
/plugin
/plugins
/pluginManagement
It overrides m-release-plugin's arguments. I suspect this will
override the -Darguments on the command line.
HTH
Ansgar
Re: Passing system arguments to the forked maven process for release:prepare and release:perform
Thanks Stephen!
Do I need to do that in the parent pom or in mine?
--
Todd Nine
On Thursday, July 12, 2012 at 2:33 PM, Stephen Connolly wrote:
Override back to ${arguments} -Psonatype-...
On Thursday, 12 July 2012, Todd Nine wrote:
Any idea how to merge the two? I obviously want command line arguments,
putting our S3 creeds into a public repo isn't a very good idea! ;)
--
Todd Nine
On Thursday, July 12, 2012 at 2:14 PM, Ansgar Konermann wrote:
Am 12.07.2012 22:33, schrieb Todd Nine:
Hi all,
I'm attempting to re-package a 3rd party open source project and
create our own custom distribution. I've modified and the source, and the
repo is available here.
https://github.com/apigee/beanstalk-spring-integration/tree/usergrid
I'm attempting to perform a release, however these properties must be
present at runtime for testing to work properly.
-DAWS_ACCESS_KEY_ID=[your aws accesskey] -DAWS_SECRET_KEY=[your aws
secret key]
Because this uses sensitive data, I obviously don't want to put these
properties in the Pom. I've scoured the documentation, but I'm unable to
find an example of how to do this, and I know I've done it before! Here is
what I'm attempting, which is failing.
mvn release:prepare release:perform
-Darguments=-DAWS_ACCESS_KEY_ID=[your aws accesskey]
-DAWS_SECRET_KEY=[your aws secret key]
Any help would be greatly appreciated!
Thanks,
This is in your parent pom (org.sonatype.oss:oss-parent:7:pom):
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.1/version
configuration
mavenExecutorIdforked-path/mavenExecutorId
useReleaseProfilefalse/useReleaseProfile
arguments-Psonatype-oss-release/arguments
/configuration
/plugin
/plugins
/pluginManagement
It overrides m-release-plugin's arguments. I suspect this will
override the -Darguments on the command line.
HTH
Ansgar
Re: Passing system arguments to the forked maven process for release:prepare and release:perform
yours since you don't control the parent
On 12 July 2012 22:35, Todd Nine tn...@apigee.com wrote:
Thanks Stephen!
Do I need to do that in the parent pom or in mine?
--
Todd Nine
On Thursday, July 12, 2012 at 2:33 PM, Stephen Connolly wrote:
Override back to ${arguments} -Psonatype-...
On Thursday, 12 July 2012, Todd Nine wrote:
Any idea how to merge the two? I obviously want command line arguments,
putting our S3 creeds into a public repo isn't a very good idea! ;)
--
Todd Nine
On Thursday, July 12, 2012 at 2:14 PM, Ansgar Konermann wrote:
Am 12.07.2012 22:33, schrieb Todd Nine:
Hi all,
I'm attempting to re-package a 3rd party open source project and
create our own custom distribution. I've modified and the source, and
the
repo is available here.
https://github.com/apigee/beanstalk-spring-integration/tree/usergrid
I'm attempting to perform a release, however these properties must
be
present at runtime for testing to work properly.
-DAWS_ACCESS_KEY_ID=[your aws accesskey] -DAWS_SECRET_KEY=[your aws
secret key]
Because this uses sensitive data, I obviously don't want to put
these
properties in the Pom. I've scoured the documentation, but I'm unable
to
find an example of how to do this, and I know I've done it before!
Here is
what I'm attempting, which is failing.
mvn release:prepare release:perform
-Darguments=-DAWS_ACCESS_KEY_ID=[your aws accesskey]
-DAWS_SECRET_KEY=[your aws secret key]
Any help would be greatly appreciated!
Thanks,
This is in your parent pom (org.sonatype.oss:oss-parent:7:pom):
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.1/version
configuration
mavenExecutorIdforked-path/mavenExecutorId
useReleaseProfilefalse/useReleaseProfile
arguments-Psonatype-oss-release/arguments
/configuration
/plugin
/plugins
/pluginManagement
It overrides m-release-plugin's arguments. I suspect this will
override the -Darguments on the command line.
HTH
Ansgar
