[jira] Created: (MECLIPSE-639) amp projects should be considered a java project

2010-02-10 Thread Erik Billerby (JIRA)
amp projects should be considered a java project


 Key: MECLIPSE-639
 URL: http://jira.codehaus.org/browse/MECLIPSE-639
 Project: Maven 2.x Eclipse Plugin
  Issue Type: Improvement
Affects Versions: 2.7
Reporter: Erik Billerby


I'm developing packages for Alfresco (large open source ECM, www.alfresco.com) 
which uses a packaging type named "amp" (Alfresco Module Package). When trying 
to generate eclipse files for my newly created maven amp archetype 
(http://maven.alfresco.com/nexus/content/repositories/alfresco-docs/maven-alfresco-lifecycle/maven-alfresco-archetypes/maven-alfresco-amp-archetype/index.html)
 by running mvn eclipse:eclipse only the .project file is created. After some 
investigation I found out the reason is that the packaging type "amp" is not 
considered to be a java project by the maven eclipse plugin. It would be much 
appreciated if you would like to add "amp" as an accepted packaging type in 
this plugin.

Thanks!
/Erik Billerby

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MCHANGES-305) Provide support for private Github repos

2013-02-28 Thread Erik Billerby (JIRA)
Erik Billerby created MCHANGES-305:
--

 Summary: Provide support for private Github repos
 Key: MCHANGES-305
 URL: https://jira.codehaus.org/browse/MCHANGES-305
 Project: Maven 2.x Changes Plugin
  Issue Type: Improvement
  Components: github
Reporter: Erik Billerby


The egit-github client provides support for both basic authentication and 
oauth. It should be pretty easy to implement in the github issue downloader. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] (MCHANGES-305) Provide support for private Github repos

2013-03-01 Thread Erik Billerby (JIRA)

 [ 
https://jira.codehaus.org/browse/MCHANGES-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik Billerby updated MCHANGES-305:
---

Attachment: github-credentials.diff

Supplied a patch that adds basic authentication for github reporting.

> Provide support for private Github repos
> 
>
> Key: MCHANGES-305
> URL: https://jira.codehaus.org/browse/MCHANGES-305
> Project: Maven 2.x Changes Plugin
>  Issue Type: Improvement
>  Components: github
>Reporter: Erik Billerby
> Attachments: github-credentials.diff
>
>
> The egit-github client provides support for both basic authentication and 
> oauth. It should be pretty easy to implement in the github issue downloader. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] (MCHANGES-305) Provide support for private Github repos

2013-03-01 Thread Erik Billerby (JIRA)

 [ 
https://jira.codehaus.org/browse/MCHANGES-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik Billerby updated MCHANGES-305:
---

Attachment: github-credentials-update.patch

The second file (named github-credentials-update.patch) is the valid one. The 
first one contained a change I made to the pom-file which was only for my local 
build.

> Provide support for private Github repos
> 
>
> Key: MCHANGES-305
> URL: https://jira.codehaus.org/browse/MCHANGES-305
> Project: Maven 2.x Changes Plugin
>  Issue Type: Improvement
>  Components: github
>Reporter: Erik Billerby
> Attachments: github-credentials.diff, github-credentials-update.patch
>
>
> The egit-github client provides support for both basic authentication and 
> oauth. It should be pretty easy to implement in the github issue downloader. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira