versioneye/versioneye_maven_plugin

versioneye.properties file should allow specification of baseUrl (and, perhaps, all properties).

Opened this issue · 2 comments

Deleted user commented

The versioneye.properties file can store the apiKey, so that one doesn't have to modify the pon.xml.
When using the Enterprise VersionEye code, the pom.xml MUST be modified to specify baseUrl.

Ideally, all the configuration parameters should be specifiable in the versioneye.properties file, so that one doesn't have to modify every project's pom.xml (at least to specify baseUrl).

The VersionEye Maven Plugin has many configuration options.

  <plugin>
    <groupId>com.versioneye</groupId>
    <artifactId>versioneye-maven-plugin</artifactId>
    <version>3.10.2</version>
    <configuration>
      <projectId>544d0ff9512592562c000003</projectId>
      <!--<apiKey>my_secret_api_key</apiKey>-->
      <!--<baseUrl>http://localhost:3000</baseUrl>-->
      <!--<proxyHost>127.0.0.1</proxyHost>-->
      <!--<proxyPort>8888</proxyPort>-->
      <!--<proxyUser>proxy_hopsi</proxyUser>-->
      <!--<proxyPassword>dont_tell_anybody</proxyPassword>-->
      <!--<updatePropertiesAfterCreate>false</updatePropertiesAfterCreate>-->
      <!--<mergeAfterCreate>false</mergeAfterCreate>-->
      <!--<parentGroupId>com.versioneye</parentGroupId>-->
      <!--<parentArtifactId>versioneye-maven-plugin</parentArtifactId>-->
      <!--<nameStrategy>name</nameStrategy>-->
      <!--<trackPlugins>true</trackPlugins>-->
      <!--<licenseCheckBreakByUnknown>true</licenseCheckBreakByUnknown>-->
      <!--<skipScopes>test,provided</skipScopes>-->
      <!--<organisation>versioneye</organisation>-->
      <!--<team>backend_devs</team>-->
      <!--<name>NameOfTheProjectAtVersionEye</name>-->
      <!--<visibility>public</visibility>-->
      <!--<ignoreDependencyManagement>false</ignoreDependencyManagement>-->
      <!--<transitiveDependencies>false</transitiveDependencies>-->
    </configuration>
  </plugin>
reiz commented

@Comet-Symphony That makes sense. That's a good feature request :)

reiz commented

@Comet-Symphony I close this ticket because it's implemented now and I just pushed it to Maven central. In ~ 1 hour you can pull down version 3.11.0 from Maven central. With that version you can even store the base URL in an ENV variable. The plugin will check the ENV variable VERSIONEYE_BASE_URL first, before it looks in the properties files.